From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Collin Peters *EXTERN*" <cpeters(at)intouchtechnology(dot)com>, <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Problems with semicolon trying to create a trigger function via jdbc |
Date: | 2010-03-26 08:26:06 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C2049EE2BD@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Collin Peters wrote:
> I have some framework code that needs to dynamically generate a
> function. There seems to be a problem where the SQL gets truncated at
> the first semicolon encountered in the function. I have tried this
> with a very simple function and duplicated it.
>
[...]
>
> Here is the rest of the details
> * JDBC version 8.3-605 JDBC 3
> * Postgres 8.3
> * JUnit 4
> * Application is built w/ Spring (but this manual query shouldn't be
> affected by taht)
> * When the above query is run through the webapp, it is initially
> triggered by a Quartz (scheduling api) trigger (which runs when the
> webapp starts)
I tried your statement with postgresql-8.3-604.jdbc3.jar and
postgresql-8.4-701.jdbc4.jar, and it worked on both.
Must be something weird...
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Migowski | 2010-03-26 11:19:16 | GUC variables in parameter URL |
Previous Message | Collin Peters | 2010-03-25 22:45:19 | Re: Problems with semicolon trying to create a trigger function via jdbc |