As to my opinion on affecting any work-arounds: I got around this issue
by not line wrapping my long strings in "EXEC SQL ..." statements that
ecpg processes.
I would edit the plpgsql function that I was writing in an external
editor, make sure it installed by copy&paste into the psql window, an
Andrew Klosterman wrote:
>
> As to my opinion on affecting any work-arounds: I got around this issue
> by not line wrapping my long strings in "EXEC SQL ..." statements that
> ecpg processes.
>
> I would edit the plpgsql function that I was writing in an external
> editor, make sure it installed
Here is an updated patch. It fixes things in the places it should be
fixed by handling \n at the time we double-quote, and double single
quotes at the place we are building the $$ string.
I am going to apply this to HEAD. It is a fix, but I am worried it
might affect ecpg users who might have w
I have researched your report, and you are right, there are two ecpg
bugs here. First, dollar quoting uses single-quotes internally to do
the quoting, but it does not double any single-quotes in the
dollar-quoted string.
Second, when a dollar quoted string or single-quoted string spans
multiple
