From: | Joel Burton <joel(at)joelburton(dot)com> |
---|---|
To: | Steve Howe <howe(at)carcass(dot)dhs(dot)org> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Catalogs design question |
Date: | 2001-10-20 04:22:30 |
Message-ID: | Pine.LNX.4.30.0110200021530.26134-100000@temp.joelburton.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 20 Oct 2001, Steve Howe wrote:
> Hello all!!
>
>
> I'm developer of a interface for PostgreSQL for the Borland Kylix
> and Delphi tools (http://www.vitavoom.com) I've run into the following
> problems with catalogs:
>
> - pg_group: the grolist field is an array. How can I make a query
> that tell me the usernames of a group ?
> - pg_proc: the proargtypes field is an array. How can I make a query
> that will link those types to the pg_types catalog ???
>
> This catalog design seems a very crude hack to make the things
> working for me. Can't those relations be separated in another table ? Or
> maybe a function that can search for a value in array, and make a wroking
> reference for an array
> element in a relation (something like "select typname from pg_type, pg_group
> where oid
> in grolist").
> I also quote the PotgreSQL user manual
> (http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/arrays.html)
In the contrib/ directory are procedures to search arrays for values.
This may help.
--
Joel BURTON | joel(at)joelburton(dot)com | joelburton.com | aim: wjoelburton
Independent Knowledge Management Consultant
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-10-20 04:54:41 | Re: To Postgres Devs : Wouldn't changing the select limit |
Previous Message | Tom Lane | 2001-10-20 03:44:44 | Re: To Postgres Devs : Wouldn't changing the select limit |