Re: pgsql vs mysql - Mailing list pgsql-general

From Jan Wieck
Subject Re: pgsql vs mysql
Date
Msg-id 44B3CBF7.2070101@Yahoo.com
Whole thread Raw
In response to Re: pgsql vs mysql  ("Merlin Moncure" <mmoncure@gmail.com>)
Responses Re: pgsql vs mysql  ("Merlin Moncure" <mmoncure@gmail.com>)
Re: pgsql vs mysql  (Scott Marlowe <smarlowe@g2switchworks.com>)
Re: pgsql vs mysql  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: pgsql vs mysql  (Roman Neuhauser <neuhauser@sigpipe.cz>)
List pgsql-general
On 6/30/2006 1:07 PM, Merlin Moncure wrote:

> * mysql has a few features here and there which are nice...just to
> name a few, flush tables with lock, multiple insert, etc

I have no clue what flushing tables with lock might be good for. Are
applications in MySQuirreL land usually smarter than the DB engine with
respect to when to checkpoint or not?

The multiple insert stuff is not only non-standard, it also encourages
the bad practice of using literal values directly in the SQL string
versus prepared statements with place holders. It is bad practice
because it introduces SQL injection risks since the responsibility of
literal value escaping is with the application instead of the driver.

Everything that teaches new developers bad things counts as a
disadvantage in my book, so -1 on that for MySQL too.


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #

pgsql-general by date:

Previous
From: "Harald Armin Massa"
Date:
Subject: Re: [pgadmin-support] Emergency - postgre is not working
Next
From: Jan Wieck
Date:
Subject: Re: Notes on converting from MySQL 5.0.x to PostgreSQL