Hi Roger,
Janssen, Roger wrote:
Hi,
Just a general question about sql statement execution.
Is it possible to force OJB not to execute a prepared statement, but to
execute the sql as a regular sql statement?
Sorry no! The use of prepared statements is deeply rooted in the OJB core.
The reason behind this is that we hit some kind of upperbound limit with
MSSQL regarding the maximum allowed number of parameters in a prepared
statement. Some of the statements that are being generated by OJB are
rejected (SQL exceptions are thrown) by MSSQL, because this upperbound
is crossed.
Maybe you can find a "hidden property" to adjust the upper bound of
maximal PS parameter.
regards,
Armin
One solution would be to not use a prepared statement in these cases.
Greetings,
Roger Janssen
*************************************************************************
The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed.You should not copy, disclose or distribute this communication
without the authority of iBanx bv. iBanx bv is neither liable for the
proper and complete transmission of the information has been maintained
nor that the communication is free of viruses, interceptions or
interference.
If you are not the intended recipient of this communication please return
the communication to the sender and delete and destroy all copies.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
