UPDATE: I noticed that I had a "rails console --sandbox" running in another window. When I quit that, the behavior of the test changed. Dramatically. I haven't sorted through the new errors, but it's clear that the --sandbox process was causing the db to respond differently.
-- 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@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
