[
https://issues.apache.org/jira/browse/CAY-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrus Adamchik updated CAY-2111:
---------------------------------
Description:
See CAY-2110... Iterated queries should unbind their internal transaction from
the current thread (still storing it in the iterator object) before returning
ResultIterator to the caller. This will remove conflicts between long running
select and any other operations a user might want to perform within the
iterator.
Side effect of this - your code will require an extra JDBC connection to
perform operations within iterator. Previously those operations reused the
connection, and it is not clear what problems this might have caused.
was:See CAY-2110... Iterated queries should unbind their internal transaction
from the current thread (still storing it in the iterator object) before
returning ResultIterator to the caller. This will remove conflicts between long
running select and any other operations a user might want to perform within the
iterator.
> Unbind transaction object from the current thread for iterated queries
> ----------------------------------------------------------------------
>
> Key: CAY-2111
> URL: https://issues.apache.org/jira/browse/CAY-2111
> Project: Cayenne
> Issue Type: Improvement
> Reporter: Andrus Adamchik
> Assignee: Andrus Adamchik
>
> See CAY-2110... Iterated queries should unbind their internal transaction
> from the current thread (still storing it in the iterator object) before
> returning ResultIterator to the caller. This will remove conflicts between
> long running select and any other operations a user might want to perform
> within the iterator.
> Side effect of this - your code will require an extra JDBC connection to
> perform operations within iterator. Previously those operations reused the
> connection, and it is not clear what problems this might have caused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
