Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1, 2.1.2, 2.1.3, 2.2.0
-
None
Description
In some environments (DB2, Oracle, PostGres) the table schema may be not equally associated with the user name, provided in the jdbc connection parameters. At the moment it is not possible to set the table schema used for the db connections.
This table schema aware datasource proxy optionally injects a schema selection sql statement into an existing database connection. It proxies a DataSource and executes an injected sql statement on every getConnection() call.
The proxy can be configured via the spring configurations files and therefore allows to add table schema support to the import functionality only. This might come in handy if you have to import into a certain table schema and cannot rely on the web application container datasource configuration that might already support table schemas (like websphere does).
The solution was inspired from http://forum.springframework.org/showthread.php?t=10728, although the runtime schema switching functionality was stripped.