db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepa Remesh <drem...@gmail.com>
Subject Re: [jira] Updated: (DERBY-614) Execution failed because of a Distributed Protocol Error
Date Fri, 17 Feb 2006 16:39:10 GMT
On 2/17/06, Kathey Marsden (JIRA) <derby-dev@db.apache.org> wrote:
>      [ http://issues.apache.org/jira/browse/DERBY-614?page=all ]
> Kathey Marsden updated DERBY-614:
> ---------------------------------
>     Other Info:   (was: [Patch available])
> I committed this change.  I noticed there is other state that is not reset in closed.
Perhaps it is guaranteed to be initialized, I don't know.  Maybe another Jira  entry to make
sure the other state is reset would be good.

I had checked all the DRDAResultSet states get initialized when
re-used. If they are not in close, they get initialized in some other
DRDAStatement methods - like addResultSet, setRsDefaultOptions,
setOPNQRYOptions, setQueryOptions etc. I will open a JIRA and post my
observations there so that this can be rechecked. I think it will be
good to add reset for all states in close() method so that we don't
miss anything by any other code changes.

View raw message