Re: Information Schema and constraint names not unique

From: Barry Lind <blind(at)xythos(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Information Schema and constraint names not unique
Date: 2003-11-07 16:51:21
Message-ID: 3FABCD89.1070505@xythos.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
>>Using tableoid instead of tablename avoids renaming problems, but makes
>>the names horribly opaque IMNSHO.
>
>
> Agreed. I think using the OIDs would be a horrible choice.
>

As a point of reference Oracle uses a naming convention of 'Cnnnn' where
nnnn is a sequence generated unique value. So in Oracle system
generated names are very opaque. I never saw this as a problem, since
if you wanted a non-opaque name you could always assign one yourself.

--Barry

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-11-07 16:53:21 Re: Experimental ARC implementation
Previous Message Bruce Momjian 2003-11-07 16:49:22 Re: PHB?