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

Re: [HACKERS] CLASSOID patch

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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


In response to

Responses

pgsql-hackers by date

Next:From: Hiroshi InoueDate: 2000-06-26 02:51:01
Subject: RE: [HACKERS] CLASSOID patch
Previous:From: Peter EisentrautDate: 2000-06-26 01:41:50
Subject: Re: [HACKERS] Re: Call for port testing on fmgr changes -- Results!

pgsql-patches by date

Next:From: Hiroshi InoueDate: 2000-06-26 02:51:01
Subject: RE: [HACKERS] CLASSOID patch
Previous:From: Peter EisentrautDate: 2000-06-25 14:32:43
Subject: Create user and transactions

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