Hi Jeff, Sorry, don't like this.
1) Defaults should be constant imho, not variable. 2) I'd suggest mySQL is just as uncommon as sqlite3 on Windows machines. Installing mySQL takes more effort and knowledge than installing sqlite3. If you want a default on a Windows machine I'd think SQL Server 2005 would be the choice, not mySQL. 3) A default is arbitrary anyways, so I'd say, let's be a fascist all the way: sqlite3. period. 4) Having one default for all systems means: less code (all 3 lines of those ;), less documentation, less confusion. I'm for mislav's suggestion that this is more a matter of documentation. And perhaps a user friendly bail message when things bomb (if that isn't given already) Regards, Lawrence > The choice to use sqlite3 as the default database was a great idea. > But it's far less common for Windows users to even know about sqlite3 > than MySQL. So right out of the gate this can present an unpleasant > experience for new users. > > I've created a patch which modifies the app generator to use sqlite3 > if the sqlite3-ruby gem can be found. If not, the default database > will revert back to MySQL. > > http://dev.rubyonrails.org/ticket/10569 > > +1 anybody? > > Thanks! > Jeff > softiesonrails.com > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
