From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | eutm(at)yandex(dot)ru |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bug of PL/pgSQL parser |
Date: | 2002-07-12 15:14:05 |
Message-ID: | 9879.1026486845@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"eutm" <eutm(at)yandex(dot)ru> writes:
> Dear Sirs!:)I encounted one small problem,working with
> PostgreSQL 7.3devel.It can look a
> bit strange,but i have to use whitespaces in names of databases,tables,fields
> and so on(like "roomno jk").It's possible to create them all and work with them
> (INSERT,DELETE,UPDATE),but PL/pgSQL parser(compiler ?) can't execute such
> statements.
Yeah, this is a known bug: the plpgsql lexer doesn't really handle
quoted identifiers correctly. (It effectively acts like double-quote
is just another letter, which of course falls down on cases like
embedded whitespace.) If you have any experience with writing flex
rules, perhaps you'd care to submit a patch.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2002-07-12 15:28:20 | Re: string cast/compare broken? |
Previous Message | Thomas Lockhart | 2002-07-12 15:07:33 | Re: workaround for lack of REPLACE() function |