Bruce Momjian <[EMAIL PROTECTED]> writes:
> I would love to know why doing this TODO item is so hard. Every time I
> ask Jan, he says it is very hard and it never gets done.
It doesn't look that hard to me, but I haven't tried yet ...
regards, tom lane
-
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I assume this completes the TODO item:
> > o Fix PL/PgSQL to handle quoted mixed-case identifiers
>
> It would if it worked, but it doesn't --- for one thing, it seems
> to allow empty identifiers (surely {DQUOTE}* should be
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I assume this completes the TODO item:
> o Fix PL/PgSQL to handle quoted mixed-case identifiers
It would if it worked, but it doesn't --- for one thing, it seems
to allow empty identifiers (surely {DQUOTE}* should be {DQUOTE}+).
I'm not convince
I assume this completes the TODO item:
o Fix PL/PgSQL to handle quoted mixed-case identifiers
It is quite a bit of lex code, but I assume it was required. No one
else was able to fix this item.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://can
I send a simple patch for PL/pgSQL parser which allow now to use whitespaces
in identifers of any kind(table names,attribute names,variables ...) in Pl/pgSQL
procedural language.Explicit definition of bug can be found in
Re: [HACKERS] Bug of PL/pgSQL parser
plpgsql.dquote.patch
Desc
