Using Tracks GTD with Postgres

I’ve started using the GTD web app Tracks to organize my lab work. When setting up Tracks, I went with PostgreSQL instead of SQLite. Why? Tracks is the perfect kind of app to couple with SQLite: single client access, not a lot of data, personal (read: undemanding) usage. However, I simply know PostgreSQL better, so it took only a few minutes to run createdb, configure database.yml, and run rake migrate. With SQLite I would have had to read the manual.

When coupled with PostgreSQL, however, there is a bug where the creation time of each Todo is not set properly. This makes every todo without a deadline instantly stale (normally, such todos become stale after 8 days).

I believe the bug is in the version of ActiveRecord (more specifically, the postgres connector) that Tracks uses. One fix is to dump the vendor/rails directory so that Tracks will use a more recent version of ActiveRecord (you’ll need to have the rails gem installed).