> Rails should add the feature to the Migrations framework regardless of > it being supported or not by the database. In the case the database > doesn't support it, it should simply create an index and it should be > left to the developers the decision of using a good database like > PostgreSQL or a bad one like MySql (Sqlite3 is being used only for > development - or at least, it should, so it shouldn't matter that much). >
No way. If you're going to add support for one database you add it for all. Just because *you* don't use one or the other does not mean you should do half assed work. Either you support each and every database equally,' or you do nothing. Ruby and Rails's support has always been that the db on the backend is relegated to basically insignificance, so you can concentrate on coding rather than the configuration. Stick to it. -- 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.
