> Ideally to test this I'd need a bunch of tables with interesting table > & column names. What's the policy on adding to the tables/models using > in tests? Just do it ? Also I noticed there's a whole bunch of files > in schema for different databases: does one need to add the > declaration for such tables to all of these files? I don't have access > to all of those dbs so it would be hard for me to be sure I hadn't > messed things up.
It would be *really* nice if we could tidy up all those active record tests to use schema.rb, thereby removing most of the hoops you have to jump through to add a table to the test schema. Unfortunately this is probably a reasonably large undertaking, so if your time is limited you're probably best off just getting it working on your own databases, making an educated guess for the others, and asking people for help testing. I personally have an EC2 image I use to test rails on all the other open source databases. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
