|Subject||Re: [Firebird-Java] Re: Hibernate 2.1.8 lazy fetch trouble with Jaybird RC 2|
> I think you're right. No transaction is used in the testcase, when IThen this is the reason.
> explicitly use a transaction the exception disappears.
> Is it possible to configure Jaybird like it will have the old, notI can add this, but the issue most likely is somewhere else... I will check
> according to the JDBC spec, behaviour? In read-only situations I don't
> always use transactions (is that bad?).
your test case to see where Hibernate executes next query.