I would also argue that even though symfony is quite easy to learn, if you're not able to install mysql (which is dead easy) and add a database (which is dead easy), symfony may not be for you.
And if options are to either have it not always working with SQLite (ie. fedora) or to have it always work with MySQL (provided MySQL is installed/available), I suggest having it always work. And (again) unless I'm mistaken, this is a problem in part related to the current version of propel (using Creole), meaning that in the not too distant future (when either propel1.3 or doctrine is stable) this issue will simply fade away, I suggest not spending too much time on it. Make MySQL a requirement, miss out on five(?) maybe-symfony users who can't cope with MySQL,. On 05/12/2007, joshua may <[EMAIL PROTECTED]> wrote: > > > I'm for using MySQL. PHP devs should generally understand MySQL. And > it's generally easier to troubleshoot than SQLite, from my experience > (as in, it's more widely use, so Google'ing error messages yields more > results) > > I can't remember why, but I had issues getting SQLite working on > Windows (not on the demo or sandbox, just on a misc app). In fact, > that was my motivation to write the Propel 1.3 plugin in the first > place. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
