On Tue, September 21, 2010 18:35, Will Bryant wrote: > On Wed, Sep 22, 2010 at 4:26 AM, James B. Byrne > <byrn...@harte-lyne.ca> wrote: >> I agree that db:migrate:whatever, when run in the development >> environment, should always produce db/schema.rb. > > It already does. The point is that unless you do a db:test:prepare, > it's not loaded into the test env yet. Whenever you run "rake" or > "rake cucumber" or anything like that, db:test:prepare is then run; > the debate here is whether it should be run at the time of migrate > rather than test.
I see. I missed the distinction. My own workflow is that after any migration then I run rake cucumber, so I would not see this problem in the normal course of events. On the other hand I do recall being tripped up by this on at least one occasion. Some sort of automation of loading the test environment dbschema driven by db:migrate seems likely a worthwhile enhancement. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
