Hi,
First of all, you can safely ignore the log message.
If you look in org.objectstyle.cayenne.dba.oracle.OracleSelectTranslator,
it tries to use some of the Oracle driver proprietary API. As DBCP wraps
statements in its own decorators, OracleSelectTranslator gives up on that
and uses vanilla JDBC.
Now if you look at the code, there are no 100% proven "optimizations" that
you'd loose. I think we should do some more research and remove this code
all together.
Andrus
> Hi there,
> I have just encountered an "Unknown Oracle Statement type" while trying
> to configure Cayenne (1.2M4) with JNDIDataSourceFactory under Tomcat
> 5.5 and DBCP with the latest Oracle9i jdbc driver (ojdbc14.jar).
>
> Here is the log trace :
>
> INFO 17/05/05 12:46:50 - QueryLogger : SELECT t0.NODEID, FROM
> IDBUSER.DICOMNODES t0 INFO 17/05/05 12:46:50 - OracleSelectTranslator :
> Unknown Oracle statement type:
> [org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement]. No Oracle
> optimizations applied. INFO 17/05/05 12:46:50 - QueryLogger : ===
> returned 165 rows. - took 188 ms. INFO 17/05/05 12:46:50 - QueryLogger :
> +++ transaction committed.
>
> The connection & query are successful, but I am worried about the "No
> Oracle optimizations applied" message : does it really have an impact
> on query performance, knowing that my queries will remain relatively
> easy and handle a charge of 2-3 calls per second ?
> What sort of Oracle optimization would Cayenne use in a normal
> situation? And, of course, how can I get rid of this "warning" and get
> my Oracle optimization back ? :-)
>
> Thanks,
> Julien Vignali
This archive was generated by hypermail 2.0.0 : Tue May 17 2005 - 10:09:18 EDT