might be a bit theoreticly thining of my own, but my motivation is here that the
application code should not necessaryly know about the schema name, as well it
does not know anything about user and password.
other hand, I researched a bit further what oracle got in this
supprisingly, there is a similar question from an
oracle user and oracle seems to have anything here either :-D
though from a theoretical point of view, this request might be to
put as set schema now in my applicational code.
Out of curiosity, and maybe a little off-topic: is there a reason to
use a separate schema, when you can use a separate database?
For example, if I have two completely unrelated applications, I think I
would create two databases, and one datasource for each:
On Oracle I may have one database with several schemas, hence the need to
specify the one I want. On Derby, would there be a benefit to reuse the same
database with multiple schemas?
Just asking off the top of my head, I haven't really tried the
On Mon, Jul 23, 2012 at 11:32 AM, Kristian Waagan <email@example.com>
SET CURRENT SCHEMA
Make your own custom
For completeness, one can also specify the schema
explicitly in the queries of course. I don't know if there are scenarios where
this approach won't work.