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

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Patrick M(dot) Rutkowski *EXTERN*" <rutski89(at)gmail(dot)com>, "Bill Moran" <wmoran(at)potentialtech(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: WARNING: nonstandard use of escape in a string literal
Date: 2009-12-24 08:14:42
Message-ID: D960CB61B694CF459DCFB4B0128514C2039380EF@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Patrick M. Rutkowski wrote:
> 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?

Precisely.

> In other words: I'm already doing it right, no?

If you define "right" as "standard compliant", yes.
If you define "right" as "in accordance with the default
behaviour of PostgreSQL", then no.

Yours,
Laurenz Albe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2009-12-24 10:10:57 Re: WARNING: nonstandard use of escape in a string literal
Previous Message S Arvind 2009-12-24 07:31:10 Session based transaction!!