Skip site navigation (1) Skip section navigation (2)

Should we drop the "object" from ORDBMS?

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: pgsql-advocacy(at)postgresql(dot)org
Subject: Should we drop the "object" from ORDBMS?
Date: 2012-04-26 06:02:19
Message-ID: 1335420139.28653.59.camel@jdavis (view raw or flat)
Thread:
Lists: pgsql-advocacy
As far as I can tell, postgresql has the following object-relational
features:

(1) OIDs -- no longer on by default for user tables, and I can't
remember seeing OIDs recommended for users. Used in system tables, but
the main special property of OIDs (that they are hidden) is annoying
more than anything else. Who wants to select from a system table without
seeing the OIDs?

(2) Inheritance -- useful feature, mostly for partitioning. Occasionally
suggested to model actual inheritance in the OO sense, but often as one
of a couple alternatives.

(3) Dot function call syntax: "select foo.count from foo" -- surprising
to most people, and I don't recall ever seeing it suggested for actual
use. I would go so far as to say we should deprecate this syntax,
because I think it's more likely to be some kind of mistake than
anything else.

Given all this, why do we still call postgres an object-relational
system (in the first sentence of our "About" page)? Is it time to drop
"object" and just call ourselves a relational (and/or SQL) system? If
someone comes to postgres for our OO support, they are probably going to
be disappointed.

Thoughts?

Regards,
	Jeff Davis


Responses

pgsql-advocacy by date

Next:From: Brendan JurdDate: 2012-04-26 06:34:23
Subject: Re: Should we drop the "object" from ORDBMS?
Previous:From: Joe ConwayDate: 2012-04-24 21:58:33
Subject: Re: LISA 2012 - Dec 9-14 San Diego

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group