On Tue, Sep 8, 2009 at 5:53 AM, Jan Ostrochovsky <jan.ostrochov...@gmail.com > wrote: > > I won't compare PostgreSQL and MySQL as whole, because: > - I do not know MySQL so well, as PostgreSQL > - another flamewar could arise ;) > > I am only saying: my experience with Django+PostgreSQL is far better, > than Django+MySQL, see > > http://groups.google.com/group/django-users/browse_thread/thread/3abfd993c3c976f9/2e410d567d4ba2db#2e410d567d4ba2db > . > If you will need some help with PostgreSQL, do not hesitate to contact > me directly. > > Jano > > On Sep 8, 2:58 am, Jason Beaudoin <jasonbeaud...@gmail.com> wrote: > > While I don't have a whole lot of experience with either, the main issue > I > > have against MySQL is it's adherence (lack, that is) to the SQL standard. > > Moving a MySQL dB--> postgreSQL needn't be so messy. > > > > I'm also a bit weary of MySQL having been bought up. > > > > Cheers, > > > > ~Jason >
@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. @Jano - Interesting post that you linked to. I've not see the same problems, though I'm not dealing with external data. I'm currently working on an internal app that will be used in Portuguese, thus dealing with UTF-8 everywhere and MySQL seems to be consuming it fine. Tho it can get a little tricky in Python code when it comes unicode characters. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
