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:

<Resource name="jdbc/app1ds" url="jdbc:derby://localhost:1527/app1db" ..... />
<Resource name="jdbc/app2ds"†url="jdbc:derby://localhost:1527/app2db" ..... />

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 above...

- Josť

On Mon, Jul 23, 2012 at 11:32 AM, Kristian Waagan <kristian.waagan@oracle.com> wrote:
On 23.07.2012 15:34, Malte.Kempff@de.equens.com wrote:
Actually I found 2 hints
  1. use SET CURRENT SCHEMA
  2. Make your own custom authentication

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.


--
Kristian