On 17 Apr 2008, at 08:24, Michael Koziarski wrote:
> >> Well the ones for which the adapters come with rails (mysql, >> postgres, >> sqlite3, sqlite (does anyone actually use sqlite non-3? there's >> currently failing tests there)) should certainly all be kept happy. I >> personally don't have the faintest clue how heavily used/important >> the >> others are. > > The other databases should be kept green by the maintainers of their > adapters. So sqlite, mysql and postgresql are the ones we're looking > after. The sqlite2 test failures are strange, is there anyone out > there using it at present? Would be good to fix this before 2.1 or at > least document the missing functionality. So, since you applied the patches I write for those issues sqlite3, mysql & postgres are all happy, sqlite2 has a single failure that I'm looking at. So far, I've left the schema files for the other databases there (along with the code in the aaa_create_tables_test) to load these (but turned off) on the ground that I wouldn't want to make it difficult for someone fix any failures this causes in other databases. Alternatively I could just blow it all away (after all that is what source control is for). Opinions ? Fred --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
