From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <darcy(at)wavefire(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, <peter_e(at)gmx(dot)net> |
Subject: | Re: Accessing schema data in information schema |
Date: | 2006-03-23 03:50:04 |
Message-ID: | 2998.24.211.165.134.1143085804.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane said:
> Darcy Buskermolen <darcy(at)wavefire(dot)com> writes:
>> On Wednesday 22 March 2006 13:11, Tom Lane wrote:
>>> (Thinks a bit...) Maybe it would work for pg_sequence to be a real
>>> catalog with a row per sequence, and we also create a view named
>>> after the sequence that simply selects from pg_sequence with an
>>> appropriate WHERE condition.
>
>> I'd think that would be a workable solution, with documentation notes
>> that this will be deprecated in favor of information_schema in an
>> upcoming release ?
>
> Yeah, we could consider the views a transitional thing, and get rid of
> them after a release or two. Tell people to change over to either look
> in the pg_sequence catalog, or use the information_schema view. Does
> that view expose everything that there is, though, or will we have
> proprietary extensions that are not in SQL2003?
>
What happens to sequence ACLs?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2006-03-23 04:00:07 | Re: Static build of psql with readline support |
Previous Message | Andrew Dunstan | 2006-03-23 03:41:47 | Re: Static build of psql with readline support |