I've run into a problem after activating the prepared statement cache for my datasource (to improve performance).
The database entries are modified from an external paplication, too. So I am using "instance per transaction" with commit option B.
With prepared statement caching enabled I don't get currently modified data displayed anymore until my connection drops and a new one gets created (this is, because the prepared statements are bound to the connection I think)
So is this to enable the prepared statement cache for a datasource which is modified by an external application?