[Hi All - I mistakenly assumed that this was a Mingle question.  I had posted a Mingle-oriented response.  I've since deleted that response. Go does not currently support SCM plugins.  In the meantime the suggested approach is to find a bridge between Plastic SCM and the support source control tools.]

Hi -

You should configure Postgres for autovacuum and we also highly recommend that you schedule a weekly manual vacuum task.  See http://www.postgresql.org/docs/8.4/static/maintenance.html for help.  

The properties "modified_on" and "created_on" are supported as both SELECTable properties and criteria in any MQL statement.  This was added in the Mingle 3.0 release.  The general MQL help page mentions that "Created On" and "Modified On" are available as predefined properties.

We did not take the decision to drop MySQL support lightly.  The decision will cause some short term pain, but once you've switched over to Postgres you should find your Mingle experience to be more pleasant.

Many Mingle features such as Property Rename, Bulk Update, and Excel Import require bulk database operations, including bulk UPDATE, bulk INSERT, and temp table usage. MySQL's locking scheme is simply not up to the task when it comes to these bulk operations.  The result is long lock waits and timeouts. We had a discussion with MySQL developers and learned that the locking issues would not be addressed in the near future.  At that point we were left with the difficult decision to phase out MySQL.

(FWIW, bulk operations are not abstracted in Rails (or any other) database adapter.  And if they were included in a db interface, that would be no guarantee that the operations 'just worked' against all databases.)

Postgres and Oracle are both top-flight databases that we feel good about supporting.  Postgres is free, open-source, and has tremendous respect within the community.  For those looking for a Postgres+Support, EnterpriseDB has a great offering which we ourselves use.

We have built migration tools that we hope will make your migration as smooth as possible.  Also, our support team is happy to help with any questions along the way, including Postgres configuration and maintenance suggestions. Moving forward, we look forward to being able to deliver features at a faster pace, due to our supporting databases that are more in line with Mingle's features.

You would have to make the following changes to the jetty.xml file, which you can find in the config folder. Please insert the line highlighted with *, changing the address to the address you wish to use, and, of course, removing the asterisks. After making the change, you will need to restart Mingle.

<!-- =========================================================== -->
<!-- Set connectors -->
<!-- =========================================================== -->
<!-- One of each type! -->
<!-- =========================================================== -->

<!-- Use this connector for many frequently idle connections and for threadless continuations. -->
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.nio.SelectChannelConnector">
<Set name="port"><SystemProperty name="mingle.port" default="8080"/></Set>
<Set name="maxIdleTime">30000</Set>
<Set name="Acceptors">1</Set>
***** < Set name="Host">127.0.0.1</Set> *****
<Set name="statsOn">false</Set>
<Set name="confidentialPort">8443</Set>
<Set name="lowResourcesConnections">1000</Set>
<Set name="lowResourcesMaxIdleTime">500</Set>
</New>
</Arg>
</Call>

Hi -

Unfortunately, you cannot use (Today) in a formula definition. The story is captured in the backlog but I am not sure when the feature might be built.

In the meantime, you have a few options:

• If there is a particular age you want to reporting against, say 14 days, you could create a property around that, say ‘Overdue On’ and it’s set to “Created On” + 14. You could then compare “Overdue On” to (Today) in MQL criteria for reports or in the cards filters.
• Write a simple script (Ruby using ActiveResource is by far the easiest) that runs once a day and re-calculates the age using the API. You would setup an ‘Age’ property as a standard date property. The script would set it to (Today) – whatever date property you wanted to use (“Created”, “Opened”, “Started”). If you have a developer with a few spare minutes this is likely the most useful solution.

• Login with a Mingle Admin account
• “All Projects”
• “Manage Users”
• Use “Admin” column to add/remove Mingle Admin privilege