public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Vik Fearing <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Karl O. Pinc <[email protected]>
Cc: [email protected]
Subject: Re: Describing Postgres as "object-relational" on the home page
Date: Tue, 26 Dec 2023 17:40:11 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Tue, Dec 26, 2023 at 10:49:16PM +0100, Vik Fearing wrote:
> On 12/26/23 22:21, Tom Lane wrote:
> > Bruce Momjian <[email protected]> writes:
> > > On Tue, Dec 26, 2023 at 01:10:47PM -0600, Karl O. Pinc wrote:
> > > > It may be better to just say "relational".
> >
> > > I guess if I had to name this with no precedence, I would call it
> > > relational/extendable, but that seems even worse that what we have.
> >
> > Call it an "extensible relational database"? I agree that the
> > "object" part is out of date and no longer much of a focal point.
>
> Especially considering we hardly implement any of the object features at
> all. We have table inheritance, and that's about it.
"extensible relational database" works for me.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Describing Postgres as "object-relational" on the home page
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox