https://bz.apache.org/bugzilla/show_bug.cgi?id=61103
--- Comment #4 from Julian Reschke <julian.resc...@gmx.de> --- Found in <https://blog.bertvanlangen.com/software-development/jdbc-statement-cache/>: "The IBM Data Server Driver for JDBC and SQLJ does not check whether the definitions of target objects of statements in the internal statement cache have changed. If you execute SQL data definition language statements in an application, you need to disable internal statement caching for that application" So caching PreparedStatements for DB2 is dangerous if it's a DDL statement, or if actually the state of the table changes between invocations (such as a transition from "does not exist" to "exist"). Now code can of course workaround this, but wouldn't it be better if the StatementCache would evict statements that have causes a non transient exception? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
