I second Jeff. On Dec 20, 2007 3:57 PM, Jeff <[EMAIL PROTECTED]> wrote:
> > On Dec 19, 10:24 pm, Lawrence Pit <[EMAIL PROTECTED]> wrote: > > Hi Jeff, > > > > Sorry, don't like this. > > > > 1) Defaults should be constant imho, not variable. > > I generally agree, but I think a reasonable degrade approach is > necessary here. > > > 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. > > I would agree with that, but since SQLServer was pulled from core in > 2.0, I don't think it would be good to make it the default in any > scenario. Of all of the open-source databases that Rails supports out > of the box in 2.0, Windows users will at least have heard of MySQL and > a little googling finds wide acceptance among big-name companies. I > think SQLLite, however, is hardly known at all. > > The scenario I'm trying to solve is this: > > 1. Windows developer wants to take the brave step of trying out Rails. > 2. She picks up any Rails book on the market, finds out she needs to > install MySQL and the Ruby One-Click Installer, and does a gem install > rails > 3. She types "rails hello_world" and creates one model > 4. Big Problems > > > 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) > > Perhaps I should change the --help text to read, "Default: sqlite3 (or > MySQL if sqlite3 gem is not found)." ? That would be fine with me. > > > > 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 -~----------~----~----~----~------~----~------~--~---
