Subject | Re: InputStream closes when prepared statement is closed. |
---|---|
Author | Roman Rokytskyy <rrokytskyy@acm.org> |
Post date | 2003-02-02T17:48:39Z |
Hi,
objects are explicitly closed in ResultSet.next() and ResultSet.close
() as required by specification.
Anyway, previous functionality could not be correctly supported.
Accessing a stream after calling Connection.commit() would fail
because there will be no valid transaction handle.
In auto-commit case streams are not closed, because content is cached
in memory anyway and there can be no inconsistencies in execution.
Best regards,
Roman Rokytskyy
> Here are the results of the test harness.I have fixed this bug for non-autocommit case. This means that Blob
> Jaybird succeeds where Interclient fails.
> In light of the above, posting will Jaybird continue to operate like
> this (i.e keep the stream open) or will it be "fixed" to mimic
> Interclient (i.e close the stream)?
objects are explicitly closed in ResultSet.next() and ResultSet.close
() as required by specification.
Anyway, previous functionality could not be correctly supported.
Accessing a stream after calling Connection.commit() would fail
because there will be no valid transaction handle.
In auto-commit case streams are not closed, because content is cached
in memory anyway and there can be no inconsistencies in execution.
Best regards,
Roman Rokytskyy