Search Postgresql Archives

Re: WARNING: nonstandard use of escape in a string literal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 23 Dec 2009, at 22:58, Patrick M. Rutkowski wrote:

> In that case, let me put it this way:
> 
> Is the query
> UPDATE my_table SET colname = NULL WHERE colname ~ '^\s*$'
> 
> already all correct and standard conforming. Such that all I need to
> do is turn on standard_conforming_strings to have it stop complaining
> at me?
> 
> In other words: I'm already doing it right, no?


Yes, for this query you are. You may have other queries that rely on non-standard escaping though, and those would break if you toggle that setting.
Alternatively you can just turn off the warning (escape_string_warning).

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.


!DSPAM:737,4b333e33228059156120885!



-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux