Thanks for your response. If we do set the JDBC-level tag to 1.0, then we lose the ability to change the ResultSet type. It may be beneficial to use different types of ResultSets in different situations.
After tracing through the code, I found that, while a boolean "scrollable" is passed into several of the functions called to perform a query, that boolean is ignored and scrollable resultsets are hard coded (except for JDBC 1.0). Is there a reason for this? I saw a comment that mentioned something about scrollable resultsets being needed for the statement caching, but I wasn't clear on why. Thanks, Matt ----- Original Message ----- From: "Mahler Thomas" <[EMAIL PROTECTED]> To: "'OJB Users List'" <[EMAIL PROTECTED]> Sent: Tuesday, December 17, 2002 3:10 AM Subject: AW: Cannot Use Forward Only ResultSets You can try to set the JDBC-level tag in repository.xml to "1.0". This will trigger usage of forward only resultsets. cheers, Thomas > -----Urspr�ngliche Nachricht----- > Von: Matt Mastrangelo [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 16. Dezember 2002 21:18 > An: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Betreff: Cannot Use Forward Only ResultSets > > > The PersistenceBroker always seems to use scrollable > ResultSets when querying using both getCollectionByQuery and > getIteratorByQuery. When using the Oracle JDBC driver, > scrollable ResultSets are stored entirely in system memory > whereas forward only ResultSets are not. Therefore, even if > you want to get only a small range of records, the entire > ResultSet is loaded into memory. > > Is it possible to specify the type of ResultSet being used by > OJB (either scrollable or forward only). > > Thanks. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
