Dictionary or Database_Please advise

mk mrkafk at gmail.com
Fri Feb 26 19:26:46 CET 2010


D'Arcy J.M. Cain wrote:

> Or PostgreSQL.  It's free, runs on lots of platforms, has good Python
> support, and there's lots of people on the net who know it and are
> willing to give help and advice.  In addition, it is a truly enterprise
> level, SQL standard, fully transactional database.  Don't start with
> MySQL and uprade to PostgreSQL later when you get big.  Start with the
> best one now and be ready.

I second that: I burned my fingers on MySQL quite a few times and don't 
want to have anything to do with it anymore. Eventually you hit the wall 
with MySQL (although I haven't tested latest and best, perhaps they 
improved).

E.g. don't even get me started on replication that tends to randomly 
fizzle out quietly without telling you anything about it. Or that 
FOREIGN KEY is accepted but referential integrity is not enforced. Or 
that if you want real transactions, you have to choose InnoDB table type 
but then you lose much of the performance. Etc.

No, if you have a choice, avoid MySQL and go for PGSQL. It's fantastic, 
if (necessarily) complex.

Regards,
mk




More information about the Python-list mailing list