> > > @Jason - I think that's the number one reason I'm going to PostgreSQL. I > don't use everything all the time but I really like to have the widest array > of query syntax options. MySQL is just too limiting, especially when > PostgreSQL is available. > > The other issue I have with MySQL is the "flexibility" to choose your own db/table engine (sorry if that isn't the correct terminology). While some find this a plus, and indeed, in *some* cases you want this sort of flexibility as some of the more obscure database environments would benefit from peculiarities of one engine over another, I don't find this sort of thing as attractive.
The reasoning is that of simplicity - as an engineer and artist, I put a lot of value in simplicity of design, implementation, and maintenance. While I don't have a lot of experience with MySQL, the more I've read about it's design and this engine "flexibility" the more I've been turned away. In my mind, it is as analogous to the linux to BSD situation.. on one hand you have a lot of flexibility (package managers, configuration tools, etc).. but in reality it turns into a total rat's nest in comparison to the "smoothness" of BSD. just my 2 cents.. ~Jason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
