What I meant was why do people still choose MySQL when PostgreSQL is a much better option all around.
I use PostgreSQL extensively and don't plan on giving up Relational DBs any time soon. I've even written an asynchronous ORM solution for postgres using Twisted. Will be released end of this month or next month. It integrates very heavily into pyjs. You can pass object graphs around between your pyjs app and the server and persist them. - lex On Wed, Apr 4, 2012 at 8:44 AM, Jeffrey Van Voorst <[email protected]> wrote: >> I think you have to be masochistic to use MySQL in this day and age :-) >> >> Does anyone even voluntarily decide to use it anymore? > > Relational databases are still good tools for certain tasks. I think > they are especially useful for persistent indexed data. I inherited a > project for which the server side is reliant on some type of storage > mechanism and it uses MySQL. I think for reasonably sized tables, > MySQL is much more fun and manageable when compared with something > like Oracle. > > On the other hand, one can use an ORM like sqlalchemy, but that > requires yet more stuff to learn and use effectively... > > By the way, databases are not "evil" or necessarily outdated. As an > example, mongrel2 stores its config in an sqlite3 database, but has a > plethora of non-SQL ways to modify its configuration (the config of > mongrel2). In my opinion, this shows that there are many instances > where a database is a good choice.
