For me SQLite is a better choice because the default database Rails uses is constant across all platforms. And maybe it's just me, but I like the idea of having a *vendor agnostic* DB used by default (we are not advertising MySQL AB that puts enterprise subscription ads even in documentation now and acts_as_enterprisey every way they can; but still for serious geospatial apps you have to go with Postgres because MySQL puts their efforts in marketing, not in database development).
On 19 дек. 2007, at 22:33, Jeff wrote: > > 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? MK --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
