Re: BUG #2228: escaped single quotes choke spi_exec_query in plperlu

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: michael <michael(at)galton(dot)ucl(dot)ac(dot)uk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2228: escaped single quotes choke spi_exec_query in plperlu
Date: 2006-02-01 15:38:29
Message-ID: 638.1138808309@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

michael <michael(at)galton(dot)ucl(dot)ac(dot)uk> writes:
> On Wed, 1 Feb 2006, Tom Lane wrote:
>> It's hardly a bug that you get a syntax error when $data contains
>> a single quote. It's up to you to construct a well-formed query
>> string to give to spi_exec_query, and this code is not doing that.

> As I understand it the input strings are correctly escaped

> INSERT INTO test VALUES ('No problem here');
> INSERT INTO test VALUES ('It''s a problem here');
> INSERT INTO test VALUES ('It\'s also a problem here');

Yeah, but by the time your trigger sees it, the data isn't escaped
anymore.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message michael 2006-02-01 15:43:13 Re: BUG #2228: escaped single quotes choke spi_exec_query in
Previous Message michael 2006-02-01 15:32:40 Re: BUG #2228: escaped single quotes choke spi_exec_query in