No need that IteratedQuery blocks the connection

From: Arndt Brenschede (a..iamos.de)
Date: Tue Feb 25 2003 - 10:11:22 EST

  • Next message: Andrus Adamchik: "Re: high-volume offline processing using cayenne?"

    Hi,

    In the documentation (as well as in
    the actual behaviour), an IteratedQuery
    blocks the jdbc-connection and the datacontext
    uses another connection from the pool
    for intermediate queries.

    There's no need for that, neither in the
    JDBC-Spec nor in what e.g. Oracle actually
    does:

    The open JDBC-Result-Set allocates the associated
    java.sql.Statement, not the java.sql.Connection,
    but a Connection can have multiple open statements!

    Not that it's a real showstopper, but Cayenne's
    behaviour on this point is really wrong
    (in terms of transactional behaviour)

    best regards,

    Arndt 

    -- 
--
Dr. Arndt Brenschede
DIAMOS AG
Innovapark
Am Limespark 2
65843 Sulzbach

    Tel.: +49 (0) 61 96 - 65 06 - 134
Fax: +49 (0) 61 96 - 65 06 - 100
mobile: +49 (0) 151 151 36 134
mailto:arndt.brensched..iamos.com
http://www.diamos.com

    This archive was generated by hypermail 2.0.0 : Tue Feb 25 2003 - 09:58:02 EST