Interesting - I upgraded to the new logging add - on recently.
W
On 2/9/11 9:00 AM, Jesse wrote:
I think this has to do with the new logging going to STDOUT, I didn't
see this until I upgraded to the new logging addon
On Feb 9, 6:44 am, chris<[email protected]> wrote:
When I run "rake db:migrate" locally, I get all of the migrations listed
out:
chris@goldfish$ rake db:migrate
(in /Users/cmcclelland/workspace/XXX)
SQL (30.0ms) SHOW client_min_messages
SQL (0.2ms) SET client_min_messages TO 'panic'
SQL (0.3ms) SET standard_conforming_strings = on
SQL (0.1ms) SET client_min_messages TO 'notice'
SQL (94.2ms) SET time zone 'UTC'
SQL (0.1ms) SHOW TIME ZONE
SQL (45.1ms) SELECT "schema_migrations"."version" FROM
"schema_migrations"
Migrating to CreateInitialTables (20100329164816)
Migrating to AddManchesterAndWorcester (20100329180447)
Migrating to MaxmindGeolocation (20100330200706)
Migrating to CreateTransactions (20100401145908)
Migrating to AddRoleMaskToUsers (20100407204815)
Migrating to CreateCreditCards (20100413144222)
Migrating to CreateDelayedJobs (20100414192906)
Migrating to AddRedemptionInstructionsToDeals (20100416155743)
Migrating to AddDefaultToCreditCards (20100416172408)
...
So, I am seeing the same behavior as on heroku.
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
