Wrong schema qualifier appended for Oracle when using JNDI data source

[Former Member]

We are facing the following problem when changing data sources at runtime using CR4E libraries version 2.2.0:

We are changing data sources to a JNDI data source, but we still need to specify a schema to qualify table names because otherwise CR adds a schema name which seems to be picking up wrongly from the DB (seems to be the first schema name defined in the DB in alphabetical order ???).

Having to specify a qualifier definitely spoil the advantage of using JNDI, which is making the code user and password agnostic.

Using unqualified table names is absolutely acceptable in Oracle, as the default schema can be specified at connection time.

This issue is the only thing forcing us to change data sources at runtime, because if CR code wouldnu2019t append a schema, the JNDI datasource will already be pointed to the right user by the container. This would bring an interesting performance improvement, which we are missing also because of this bug.

Is it ant way we can indicate the CR lib code not to append a schema to the tables when querying?

Thanks

---

Juan

[Former Member]

Based on the number of requests for details about JNDI data source usage related to Oracle, I think the resolution of the mentioned bug could be of high interest for an important number of CR users besides my company.

Could somebody from CR comment on this thread, please?

Ted?

Thanks

---

Juan