db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <Malte.Kem...@de.equens.com>
Subject AW: Derby memory consumption with many databases
Date Thu, 07 Jan 2010 17:05:31 GMT
Hi to all who know more about Derby
In this particular situation mentioned below, is it possible
to work with views that are able to use the certain table of the 
particular schema of the user that is loged in.
It is just a thought that may be then the db abstraction layer Cayenne
provides still is able to work....(?)

-----Ursprüngliche Nachricht-----
Von: Øyvind Harboe [mailto:oyvind.harboe@zylin.com] 
Gesendet: Donnerstag, 7. Januar 2010 17:37
An: Derby Discussion
Betreff: Re: Derby memory consumption with many databases

> In case you go that route, I just thought I'd mention here that Derby
> supports standard SQL schemas and SQL authorization (so users would be
> protected from accessing each others schemas) in contrast to
> e.g. MySQL, for which database and schema is more or less the same
> thing.

The problem I have with schemas is that it isn't really portable between

We would like to leave the database choice to the users. Our app is
talking to Cayenne which provides the db abstraction.

Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer

View raw message