Re: Humor me: Postgresql vs. MySql (esp. licensing)

From: Jonathan Bartlett <johnnyb(at)eskimo(dot)com>
To: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
Cc: John Wells <jb(at)sourceillustrated(dot)com>, PostgreSQL general list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Humor me: Postgresql vs. MySql (esp. licensing)
Date: 2003-10-08 17:01:03
Message-ID: Pine.GSU.4.44.0310080955310.28199-100000@eskimo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> > It's my opinion that we should be using PG, because of the full ACID
> > support, and the license involved. A consultant my company hired before
> > bringing me in is pushing hard for MySql, citing speed and community
> > support, as well as ACID support.
>

The fact is that PG has features that MySQL doesn't have that are REALLY
needed. The big ones being views, subselects, functions, triggers, and
constraints. Small queries run by a few users may run faster on MySQL.
When you get to real queries by large groups, it almost always favors PG.
In fact, as youre application grows, you will find MySQL completely
useless. I always get frustrated when MySQL is touted as a great
open-source database. Especially when the field is very rich - PG, SAP,
and Firebird all come to mind.

Jon

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sibusiso xolo 2003-10-08 17:11:05 problems retrieving images in 7.3.4
Previous Message Bill Gribble 2003-10-08 16:56:48 Re: Humor me: Postgresql vs. MySql (esp. licensing)