> 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 ?
I think it's all good to clear those out entirely, so just upload a patch (using git format-patch on your branch) to wrap this up, and I'll apply it. -- 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 -~----------~----~----~----~------~----~------~--~---
