Message-ID: <42A470FA.1080001@comcast.net>
Date: Mon, 06 Jun 2005 11:51:22 -0400
From: Jeffrey Tenny <jeffrey.tenny@comcast.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: Need help to decide Mysql vs Postgres
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Re: your JDBC wishes: Consider IBM Cloudscape (now Apache Derby) too, 
which has an apache license.  It's all pure java and it's easy to get going.


As to MySql vs Postgres: license issues aside, if you have 
transactionally complex needs (multi-table updates, etc), PostgreSQL 
wins hands down in my experience.  There are a bunch of things about 
MySQL that just suck for high end SQL needs. (I like my subqueries,
and I absolutely demand transactional integrity).

There are some pitfalls to pgsql though, especially for existing SQL 
code using MAX and some other things which can really be blindsided 
(performance-wise) by pgsql if you don't use the workarounds.


MySQL is nice for what I call "raw read speed" applications. But that 
license is an issue for me, as it is for you apparently.


Some cloudscape info:
http://www-306.ibm.com/software/data/cloudscape/

Some info on pitfalls of MySQL and PostgreSQL, an interesting contrast:
http://sql-info.de/postgresql/postgres-gotchas.html
http://sql-info.de/mysql/gotchas.html