Re: Is there a drawback when changing NAMEDATALEN to 64?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bill McGonigle <mcgonigle(at)medicalmedia(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Is there a drawback when changing NAMEDATALEN to 64?
Date: 2002-02-27 03:22:45
Message-ID: 200202270322.g1R3MkC04561@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bill McGonigle wrote:
>
> On Thursday, January 24, 2002, at 06:53 , Tom Lane wrote:
>
> > BTW, I noticed the other day that both SQL92 and SQL99 specify the
> > maximum identifier length as 128. So really there is a standardization
> > argument for pushing it up to 128 ...
>
> Yeah, I realize this was a month ago. :)
>
> One question: What is an identifier defined as? The reason I'm being
> pendantic is that I've run into trouble not with any particular table or
> column name being > 32, but the automated key name generated for tables
> with a NOT NULL UNIQUE column is table_column_key, which easily busts
> the limit.
>
> The reason I ask is because if an identifier is only defined as
> something like a column name or table name, then NAMEDATALEN would have
> to be 128+128+5, if I did the math right.

I guess we just hope then don't max out the fields as much as they do
with the 32 limit. Theoretically, yes, you could still overflow the
limit.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adam 2002-02-27 04:16:29 Re: setting up a trace through extended stored procedures
Previous Message Thomas T. Thai 2002-02-27 03:16:36 Re: help with getting index scan