From: | "Sabin Coanda" <sabin(dot)coanda(at)deuromedia(dot)ro> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: show value of backslashes in string array argument |
Date: | 2007-11-12 17:12:36 |
Message-ID: | fha1hr$25gm$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in message
news:6268(dot)1194883527(at)sss(dot)pgh(dot)pa(dot)us(dot)(dot)(dot)
> That's how it's supposed to be. See
> http://www.postgresql.org/docs/8.2/static/arrays.html#AEN5876
Hi Tom,
I read it and I understood there are 2 cascaded parsers, but I didn't find
an explicit reference to the behavior related to
standard_conforming_strings.
But after some tests, I found the following behaviors:
- the 1st parser is the SQL interpreter which is aware of
standard_conforming_strings (on or off)
- the 2nd parser which is an array interpreter, doesn't care of
standard_conforming_strings, using every time C escape conventions
Please confirm me whether I understand it correctly or not.
TIA,
Sabin
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Joseph Krogh | 2007-11-12 20:27:14 | Problem with UNION-queries |
Previous Message | Sabin Coanda | 2007-11-12 16:19:13 | Re: plpgsql language not aware of standard_conforming_strings ? |