Hallo Rainer,
We are using Oracle 11g, and so the oracle driver within EmpireDB.
As far as I know the jdbc driver (ojdbc6, through C3P0) does not really
matter, as the problem happens during the construction of the sql, so
purely within my application and EmpireDB.
//Alain
On 28/02/2013 09:24, Rainer Döbele wrote:
Hallo Alain,
if you do a lot of inserts like that, then it would be wise to use prepared
statements.
Not only will they probably solve your problem but they should also be
considerably faster.
You can simply enable prepared Statements
(DBDatabase.setPreparedStatementsEnabled(true)).
But of course it seems to be a bug that has got to be found.
Please let me know which DBMS and database driver you are using.
And - if possible - let us know, if the prepared statement approach worked for
you.
Regards
Rainer
