Re: BUG #15632: Correctly escaped strings are mishandled in function - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #15632: Correctly escaped strings are mishandled in function
Date
Msg-id CAKFQuwbLQMgEiVH=W4_4zHvNMd90+HPhs3ZiYCvQFZE5Q7uMcQ@mail.gmail.com
Whole thread Raw
In response to BUG #15632: Correctly escaped strings are mishandled in function  (PG Bug reporting form <noreply@postgresql.org>)
Responses RE: BUG #15632: Correctly escaped strings are mishandled in function  (Kaleb Akalework <kaleb.akalework@asg.com>)
RE: BUG #15632: Correctly escaped strings are mishandled in function  (Kaleb Akalework <kaleb.akalework@asg.com>)
List pgsql-bugs
On Mon, Feb 11, 2019 at 11:04 AM PG Bug reporting form
<noreply@postgresql.org> wrote:
> I'm working on a Java app, and I used prepared statements to create a
> function call to postgressql.

PostgreSQL (one s)...

> Inside my function I take these parameters and build a query like this
>  WITH upd AS (  UPDATE topic$_dept  SET topic_value =  'SOLD''   WHERE
> topic_value = 'SOLD'  RETURNING 1 )  SELECT COUNT(*) FROM upd

I doubt this is a bug but rather likely you are not doing something
correctly here.  But since you don't show the function its impossible
to say what.

> This will throw an error

How hard is it to include the actual error?

David J.


pgsql-bugs by date:

Previous
From: "Abhilash Mannathanil (amannath)"
Date:
Subject: Re: Error "new timeline 2 forked off current database systemtimeline" in cascaded replication, when master changes
Next
From: Kaleb Akalework
Date:
Subject: RE: BUG #15632: Correctly escaped strings are mishandled in function