Subject | Re: Migrating from Interclient to JayBird |
---|---|
Author | Roman Rokytskyy |
Post date | 2003-06-24T19:34:48Z |
Hi,
party component?
specification. For example, specification does not allow to call
commit() in autocommit mode, so JayBird will not allow it under no
circumstances (at least should not :).
Please, post your stack tarce, we should be able to tell you more.
Best regards,
Roman Rokytskyy
> What is happenning is the following. We create a connection usingIs there any chance that Connection.commit() is called from some third
> defaults and, when we run it, an exception is thrown every SQL
> query. It says: "commit called with AutoCommit true!". Interesting
> that we are not calling any explicit commit; also this code used to
> work just fine with Interclient.
party component?
> To try to avoid this exception, we included a call toCan you include complete stack trace?
> Connection.setAutoCommit(false) before any transaction. The first
> exception is not thrown anymore; however some other exceptions are
> thrown ("FBSQLException: GDS exception. Dynamic SQL Error", is an
> example) and the application starts behaving strangely.
> Do you know why would this happen?Without stack trace - no.
> Does not JayBird support AutoCommit mode?It does. But JayBird is a little bit paranoid in implementing
specification. For example, specification does not allow to call
commit() in autocommit mode, so JayBird will not allow it under no
circumstances (at least should not :).
Please, post your stack tarce, we should be able to tell you more.
Best regards,
Roman Rokytskyy