Re: Information Schema and constraint names not unique - Mailing list pgsql-hackers

From Barry Lind
Subject Re: Information Schema and constraint names not unique
Date
Msg-id 3FABCD89.1070505@xythos.com
Whole thread Raw
In response to Re: Information Schema and constraint names not unique  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Information Schema and constraint names not unique  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: What do you want me to do?
Next
From: Tom Lane
Date:
Subject: Re: stats collector causes shared-memory-block leakage