From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Chris Bitmead <chris(at)bitmead(dot)com> |
Cc: | 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 01:41:58 |
Message-ID: | Pine.LNX.4.21.0006260323310.11966-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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.
Secondly, maybe we ought to make the name less susceptible to collision by
choosing a something like _CLASSOID (or whatever).
> It works!
Great! :)
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-06-26 02:51:01 | RE: [HACKERS] CLASSOID patch |
Previous Message | Peter Eisentraut | 2000-06-26 01:41:50 | Re: [HACKERS] Re: Call for port testing on fmgr changes -- Results! |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-06-26 02:51:01 | RE: [HACKERS] CLASSOID patch |
Previous Message | Peter Eisentraut | 2000-06-25 14:32:43 | Create user and transactions |