From: | Vladimir Kokovic <vladimir(dot)kokovic(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: too many dotted names |
Date: | 2011-04-07 06:44:44 |
Message-ID: | BANLkTincEea-T2zoA_3GqFHeNuQ4+8+YYw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/7/11, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Apr 6, 2011 at 4:23 PM, Vladimir Kokovic
> <vladimir(dot)kokovic(at)gmail(dot)com> wrote:
>> Hi,
>>
>> Does it make sense to treat these ?
>>
>> ALTER TABLE "s'd"".s'd"""."s's'd""." ADD COLUMN id bigint DEFAULT
>> nextval('"s''d".s''d""."s''d".d"s''"');
>>
>> ERROR: improper relation name (too many dotted names): s'd.s'd"".s'd.d"s'"
>> SQL state: 42601
>
> Treat them as what?
Even nextval('"s''d".s''d""."s''d".d"s''"') is correct literal,
PostgreSQL parser treats them like error.
I think that only solution is to prohibit ". (double quote and dot) to
be part of schema or sequence name.
Best regards,
Vladimir Kokovic, DP senior, Belgrade, Serbia
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-04-07 06:56:34 | Re: Failed assert ((data - start) == data_size) in heaptuple.c |
Previous Message | Greg Smith | 2011-04-07 06:13:33 | Re: Postgresql on multi-core CPU's: is this old news? |