From: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Chris Bitmead <chris(at)bitmead(dot)com>, Postgres Hackers List <hackers(at)postgresql(dot)org>, "pgsql-patches(at)postgresql(dot)org" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] CLASSOID patch |
Date: | 2000-06-26 04:48:13 |
Message-ID: | 3956E08D.530B334A@nimrod.itg.telecom.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Chris Bitmead wrote:
>
> Peter Eisentraut wrote:
> >
> > Chris Bitmead writes:
> >
> > > Attached is a first attempt at implementing the classoid feature.
> >
> > I'm wondering what other people think about the naming. Firstly, it's my
> > feeling that TABLEOID would be more in line with the general conventions.
>
> I was thinking this myself today. Mainly because I wonder if in the
> future there may be support for more than one table implementing a
> particular class type. On the other hand the oid is a reference to the
> pg_class table. Maybe pg_class should be renamed pg_table? Anyway, my
> current thinking is that tableoid is better.
Or put another way, I see SQL3 has a feature S051 "CREATE TABLE
<tablename> OF <type>", and it seems maybe the <type> should be called a
class, and the table a collection of that class. This would advocate the
tableoid name I think. Someone please correct me if my thinking is
muddled here.
From | Date | Subject | |
---|---|---|---|
Next Message | Ed Loehr | 2000-06-26 04:56:24 | Re: Server process exited with status 139 (meaning?) |
Previous Message | Tom Lane | 2000-06-26 04:35:44 | Re: Server process exited with status 139 (meaning?) |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-06-26 10:18:48 | RE: [HACKERS] CLASSOID patch |
Previous Message | Chris Bitmead | 2000-06-26 03:36:48 | Re: CLASSOID patch |