Still on the same line, would there be any conflict between the OJB batch execution mode implementation if prepared statements were cached?
-----Original Message----- From: Cassio Souza Sent: Friday, May 13, 2005 3:57 PM To: OJB Users List Subject: caching prepared statement H, iI'm running into a limit on the number of open statements within a long connection using DB2 and as I looked into what controls OJB gave to me to re-use existing prepared statements instead of creating new ones, it is not clear what I can do. Has anyone experinced the same kind of problem and knows how to deal with it? I looked into class SQLCachingStatementsForClass but it doesn;t seem that it is caching the JDBC prepared statements, just the generated SQL string. Should I define another implementation of StatementsForClassIF, maybe a subclass of StatementsForClassImpl, to cache the PreparedStatement and re-use them within a transaction, or is this not possible due to some constraints with the OJB architecture? Or is there another way to achieve it that I might be missing? Thanks in advance for any help, Cassio Souza --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
