Re: Postgres 8.4 literal escaping

On Jul 9, 2:18 pm, t(dot)(dot)(dot)(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote:
> Niederland <niederl(dot)(dot)(dot)(at)gmail(dot)com> writes:
> > SQL 2: select ('A' || '\r\n' || 'B') as tt from customer limit 1
> > Functions without escaping literal
>
> Really?  I get
>
> regression=# select ('A' || '\r\n' || 'B') as tt from customer limit 1;
> WARNING:  nonstandard use of escape in a string literal
> LINE 1: select ('A' || '\r\n' || 'B') as tt from customer limit 1;
>                        ^
> HINT:  Use the escape string syntax for escapes, e.g., E'\r\n'.
>  tt
> ----
> (0 rows)
>
>                         regards, tom lane
>
> --
> Sent via pgsql-general mailing list (pgsql-gene(dot)(dot)(dot)(at)postgresql(dot)org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-general

Verified your results via psql, you were correct as always.

I was using pgadmin and did not realize after that running the select
query the pgadmin automatically showed the Data Output tab (and the
escape warning was in the hidden Messages tab), but when runing the
update query the pgadmin jumped to the Messages tab showing the escape
warning).