Re: Information Schema and constraint names not

At 10:54 AM 7/11/2003, Philip Warner wrote:
>add table OID (or something else) to the information schema

Peter may have been alluding to this, and I misunderstood, but one idea 
might be to present a mangled name in the information schema; since the 
spec expects them to be unique, perhaps the schema should present them as 
unique. Downside is that named constraints would also have to be mangled. A 
compromise would be to only mangle the '$n' constraints, and just prepend 
'pg_<tablename>' to the constraint name in the view.



----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 03 5330 3172          |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                 |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/