On Thu, 2006-02-23 at 17:08 +0100, Roman Rokytskyy wrote:

> > Things most likely changed and for a good reason. However if this does
> > not sound like the result of a modification to Jaybird.
>
> It is. We have now JDBC-specs conformant behavior in auto-commit mode. See
> release notes and JDBC specs for information when result set is closed.

Ok, that would explain OO. However my apps do not use auto-commit mode.
I either commit or rollback within the apps. Will hit up specs though as
well.

> > Then a bug? Or improper usage? I have little to know control over how OO
> > accesses the db, transaction wise and etc. (At least to my knowledge)
> >
> > Any thoughts, comments, feedback, etc is all greatly appreciated.
>
> We need somehow to switch the auto-commit mode off. On the other hand, I
> think we can add in next release a parameter that would construct holdable
> result sets by default (in that case result set won't be closed but cached
> completely in memory).

That would be cool. It's just sometimes I use the data from one result
set with data from another result set. Before I have close the first. At
the moment I have done a temp work around by storing the values of the
first result set in variables. To be used with the next. I very well
could be going about things incorrectly. However cached result sets
would make most of this all go away for me. If it's not against spec or
etc. I see no reason not to add/include that support.

Thanks for the info. In the mean time I have just reverted back to 1.5.6
for OO. I will keep using 2.0.1 for everything else.

--
Sincerely,
William L. Thomson Jr.
Obsidian-Studios, Inc.
http://www.obsidian-studios.com