From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Regina" <lr(at)pcorp(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4843: non standard use string literal warning in RAISE WARNING |
Date: | 2009-06-08 13:57:35 |
Message-ID: | 12158.1244469455@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Regina" <lr(at)pcorp(dot)us> writes:
> I'm not sure if this is a bug or expected behavior. But in a new PostGIS
> function we are writing, we are getting a
> WARNING: nonstandard use of \' in a string literal HINT: Use to write
> quotes in strings, or use the escape string syntax (E'...').
> With sections of the code that look like
> RAISE WARNING 'Not inserting \'%\' in \'%.%\' into geometry_columns: could
> not determine ndims', quote_ident(gcs.attname), quote_ident(gcs.nspname),
> quote_ident(gcs.relname);
> The same function on 8.3.7 does not do this.
This is an intended change: RAISE format strings are now processed the
same as any other string literal. Personally I'd suggest using '' here
rather than \' --- more standard, more future-proof, etc.
(Hmm, there seems to be nothing about it in the release notes ... not
sure how we overlooked that.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2009-06-09 06:15:38 | Cursor with hold emits the same row more than once across commits in 8.3.7 |
Previous Message | Regina | 2009-06-08 04:48:58 | BUG #4843: non standard use string literal warning in RAISE WARNING |