From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | kaleb(dot)akalework(at)asg(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15632: Correctly escaped strings are mishandled in function |
Date: | 2019-02-11 18:19:04 |
Message-ID: | CAKFQuwbLQMgEiVH=W4_4zHvNMd90+HPhs3ZiYCvQFZE5Q7uMcQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Feb 11, 2019 at 11:04 AM PG Bug reporting form
<noreply(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Kaleb Akalework | 2019-02-11 18:22:20 | RE: BUG #15632: Correctly escaped strings are mishandled in function |
Previous Message | Abhilash Mannathanil (amannath) | 2019-02-11 18:04:02 | Re: Error "new timeline 2 forked off current database system timeline" in cascaded replication, when master changes |