> 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,. >
I've read on the propel mailinglist that 1.3 is already more stable than 1.2 because of the extensive testing that's already put into it, and it may be released as stable this month. The only big remaining issue is with the new native NestedSet feature and that won't bite unless you use it. I've been using it for a few weeks now working on a new project and I have yet to find a bug. It doesn't log queries to the debugbar yet but I think that's as good as fixed. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
