"Tom Lane" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> 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
"Sabin Coanda" <[EMAIL PROTECTED]> writes:
> I found that, is that in spite of using standard_conforming_strings = 'on',
> the string array items are shown in C escape sequences conventions.
That's how it's supposed to be. See
http://www.postgresql.org/docs/8.2/static/arrays.html#AEN5876
Στις Δευτέρα 12 Νοέμβριος 2007 11:51, ο/η Sabin Coanda έγραψε:
> I fond another collateral problem, because there are the different
> convention to describe a varchar array item which contains backslashes,
> when standard_conforming_strings = 'on'
>
> For instance, to get a string composed by just
I fond another collateral problem, because there are the different
convention to describe a varchar array item which contains backslashes, when
standard_conforming_strings = 'on'
For instance, to get a string composed by just one character backslash I can
use any of the two forms:
SELECT A
If you do
SELECT "colVarchar","colVarcharArray"[1] FROM test;
you will see that you get identical values.
--
Achilleas Mantzios
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Hi there,
I have a problem using backslash character as part of a string array item.
I use "PostgreSQL 8.2.4 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC)
3.4.2 (mingw-special)" version, with standard_conforming_strings = 'on'.
I found that, is that in spite of using standard_conforming_str
