Hi Jens,
interesting posting!
I think You still could get the JDBC source code (since it is open source
now and there is a download option for it). Maybe, the bug is in jdbc, not
the sapdb itself. Then You could fix it (maybe running a 36h debug session
;-) and post the fix. I mean, isn't it this open source is all about?
I have a side question: I've set up Firebird and SapDB successfully with our
EJB application. Performance seems to be the same while SapDB has much more
options and Firebird has a much smaller footprint.
Can You give any hint when to use which database? They are bith open source
and both seem solid software.
Bye,
Falk
----- Original Message -----
From: "Jens Stutte" <[EMAIL PROTECTED]>
> com.sap.dbtech.jdbc.exceptions.DatabaseException: SAP DBTech SQL: [750]
Too
> many SQL statements (work rolled back)
> I talked with someone from SAP and they told me, that there is a limit of
> "several million statements" that can be executed within one open
> connection, then it quits work (it does not matter, if these statements
are
> within different transactions, it's a per session limit). Clearly, this is
a
> SAP problem, but i tried to avoid it with orion's datasource settings.
While
