RE: JT400 / JTOpen Statement Pooling

Etienne, I think you need to speak more directly to the JTOpen JDBC
developers.  I'm not sure how you're getting from the JDBC 3.0 application
specification (that simply says the data layer MAY reuse statements) to the
fact that you expect specific physical actions.  What happens under the
covers is not under your control (I think this is a stupid concept, but that
seems to be the direction JDBC is moving).


> From: Etienne Richards
>
> Joe,
>
> 1. Statements Pool (Caching)
> When creating a prepared statement (with default settings) the JT400 jdbc
> driver communicates with the AS/400. When I then execute the prepared
> statement the jdbc driver will again communicate with the AS/400.
> If I were
> to prepare the same statement on the same connection I see the jdbc driver
> communicating for the prepared and for the execute (The statement has
> already been prepared on the connection and there is no need to
> communicate
> with the AS/400 when preparing the same statement on the same connection).
> http://www-106.ibm.com/developerworks/java/library/j-jdbcnew/  (Prepared
> statement pooling)
>
> When I have extended dynamic enabled I do not see the jdbc driver
> communicating with the AS/400 if I were to prepare a statement
> for a second
> time (if it was already prepared on the connection). For this to be work
> properly you must use parameter markers in the sql statement.