Re: Information Schema and constraint names not unique

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Barry Lind <blind(at)xythos(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 21:25:21
Message-ID: 200311072125.hA7LPLU27930@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Barry Lind wrote:
>
>
> 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.

What, no dollar signs? :-)

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-11-07 21:26:29 Re: What do you want me to do?
Previous Message Tom Lane 2003-11-07 21:16:15 Re: stats collector causes shared-memory-block leakage