Re: postgre vs MySQL

From: Thomas Pundt <mlists(at)rp-online(dot)de>
To: pgsql-general(at)postgresql(dot)org, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: "paul rivers" <rivers(dot)paul(at)gmail(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Ivan Sergio Borgonovo" <mail(at)webthatworks(dot)it>
Subject: Re: postgre vs MySQL
Date: 2008-03-13 08:25:48
Message-ID: 200803130925.48194.mlists@rp-online.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Donnerstag, 13. März 2008, Scott Marlowe wrote:
| My real complaint with InnoDB is it's a red headed step child.  If
| mysql supported only innodb, it would be a very different database,
| and probably a bit simpler as well.  no need to worry about how you
| state fk-pk relationships (currently column level references are
| silently dropped for innodb OR myisam).  If there was a run time
| switch that said "use only innodb and use syntax that's sane" I'd
| probably be willing to test that out.

To be fair, MySQL-5 has such a switch (kind of):

http://dev.mysql.com/doc/refman/5.0/en/faqs-sql-modes.html

You can set the @@sql_mode variable to a value, that MySQL almost behaves
like standard SQL (I've not tested this by myself, though).

Ciao,
Thomas

--
Thomas Pundt <thomas(dot)pundt(at)rp-online(dot)de> ---- http://rp-online.de/ ----

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2008-03-13 08:51:29 Re: Relocation error:/usr/lib/libpq.so.5:undefinedsymbol: krb5_cc_get_principal
Previous Message josep porres 2008-03-13 08:25:20 Re: porting vb6 code to pgplsql, referencing fields