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...
In response to
pgsql-jdbc by date
|Next:||From: Daniel Migowski||Date: 2010-03-26 11:19:16|
|Subject: GUC variables in parameter URL|
|Previous:||From: Collin Peters||Date: 2010-03-25 22:45:19|
|Subject: Re: Problems with semicolon trying to create a trigger function via jdbc|