From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Curt Sampson <cjs(at)cynic(dot)net> |
Cc: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Copeland <greg(at)CopelandConsulting(dot)Net>, PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Why is MySQL more chosen over PostgreSQL? |
Date: | 2002-08-02 11:07:56 |
Message-ID: | 1028286476.14586.30.camel@taru.tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 2002-08-02 at 08:55, Curt Sampson wrote:
> On Fri, 2 Aug 2002, Marc G. Fournier wrote:
>
> > Isn't inheritance kinda one of those things that is required in order to
> > be consider ourselves ORBDMS, which we do classify our selves as being?
>
> Well, it depends on what you call an ORDBMS. By the standards of
> Date and Darwen in _The Third Manifesto_,
Is _The Third Manifesto_ available online ?
> table inheritance is not
> required and is in fact discouraged as a feature trivially implemented
> with views, foreign keys and constraints. (Though that does not
> mean that posgresql currently has an implementation of these that
> will make it trivial.)
Could you brief me why do they discourage a syntactical frontent to a
feature that is trivially implemented ?
If it is just views. foreign keys and constraints anyway, it should not
add compexity to implementation.
OTOH, stating explicitly what you mean, can give the system extra hints
for making good optimisation decisions.
-------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-08-02 11:10:47 | Re: Why is MySQL more chosen over PostgreSQL? |
Previous Message | Hannu Krosing | 2002-08-02 10:56:12 | Re: Open 7.3 items |