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

Re: [RFC] Common object property boards

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kohei Kaigai <kohei(dot)kaigai(at)emea(dot)nec(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, "robertmhaas(at)gmail(dot)com" <robertmhaas(at)gmail(dot)com>
Subject: Re: [RFC] Common object property boards
Date: 2011-08-01 20:02:39
Message-ID: 1312228815-sup-7661@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Excerpts from Kohei KaiGai's message of dom jul 31 02:21:55 -0400 2011:
> 2011/7/29 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> > It would likely be better to not expose the struct type, just individual
> > lookup functions.
> >
> If so, individual functions to expose a certain property of the supplied
> object type should be provided.
> 
>   int get_object_property_catid_oidlookup(ObjectType);
>   int get_object_property_catid_namelookup(ObjectType);
>   Oid get_object_property_relation_id(ObjectType);
>   AttrNumber get_object_property_nameattnum(ObjectType);
>   AttrNumber get_object_property_namespacenum(ObjectType);
>   AttrNumber get_object_property_ownershipnum(ObjectType);

Maybe a single lookup function that receives pointers that the lookup
routine can fill with the appropriate information; allowing for a NULL
pointer in each, meaning caller is not interested in that property.

-- 
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2011-08-01 20:02:45
Subject: Re: Compressing the AFTER TRIGGER queue
Previous:From: Tom LaneDate: 2011-08-01 19:53:19
Subject: Re: Compressing the AFTER TRIGGER queue

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