I added some db specific constraints. I wanted to test them and tweak them. So, I have unit tests. But, I was amazed to see all of the pass the first time. So, I looked and the test database does not have any constraints. I''m using PostgreSQL. Is there an option to rake db:test:prepare ? Thank you, Perry -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On Jul 14, 2007, at 18:54 , Perry Smith wrote:> I added some db specific constraints.> So, I looked and the test database does not have any constraints.How did you add the db-specific constraints? I suspect you need to use config.active_record.schema_format = :sql in environment.rb. Michael Glaesemann grzm seespotcode net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Perry Smith wrote:> I added some db specific constraints. I wanted to test them and tweak > them. So, I have unit tests. But, I was amazed to see all of the pass > the first time. > > So, I looked and the test database does not have any constraints. I''m > using PostgreSQL. Is there an option to rake db:test:prepare ?I''m not sure why this isn''t one tiny bit smoother, but you typically have to use lines like rake RAILS_ENV=test db:migrate rake RAILS_ENV=test db:test:prepare rake RAILS_ENV=test db:fixtures:load You only need to do the first one, once, after adding migrations that add new database details. I don''t think normal development requires the second two. The deal is ''rake test'' internally switches RAILS_ENV to test mode, but most other rake commands do not. In extremis (meaning very often) we must ''drop database'' inside our database (MySquirrel) to then run db:migrate to get a fresh and up-to-date version. And props for unit testing! -- Phlip http://www.oreilly.com/catalog/9780596510657/ "Test Driven Ajax (on Rails)" assert_xpath, assert_javascript, & assert_ajax --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---