Re: Why is MySQL more chosen over PostgreSQL?

From: Curt Sampson <cjs(at)cynic(dot)net>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Don Baccus <dhogaza(at)pacifier(dot)com>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is MySQL more chosen over PostgreSQL?
Date: 2002-08-09 01:38:38
Message-ID: Pine.NEB.4.44.0208091035330.3399-100000@angelic.cynic.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8 Aug 2002, Hannu Krosing wrote:

> The main difference (in the inheritance part) is that a relation does
> not have one fixed set of fields, but can have any additional fields
> added in inherited tables and still be part of to the base table as
> well.

This is trivial to do with a view.

> Actually I am not against ripping out the current broken implementation,
> but not before there has been a new, correct model available for at
> least two releses, so that people have had time to switch over.

So in other words, you want to let people use broken stuff, rather
than switch to another method, currently available, that has all
of the functionality but is not broken. I guess that's an opinion, all right.

> VIEWs are broken too, in the sense that you can't insert into them
> without doing some hard work.

Views are missing functionality. That is rather different from
making other tables lie about what they contain, essentially
destroying the requested data integrity.

cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2002-08-09 01:46:05 Re: Why is MySQL more chosen over PostgreSQL?
Previous Message Rod Taylor 2002-08-09 01:10:23 Documentation BuildLog