I thought that you could also do this by modifying
org/apache/derby/module.properties (as available in your classpath).
I'm not sure what entry to modify, but this is what is used to identify
what implementation use for various interfaces (such as StorageFactory).
David
Francois Orsini wrote:
Luigi,
On 3/29/07, Francois Orsini <[EMAIL PROTECTED]> wrote:
Regarding A) You might want to look at some of the proposed and pending
changes for in-memory database / storage support:
https://issues.apache.org/jira/browse/DERBY-646
Check the very first comments as a possible way.
You would
Regarding A) You might want to look at some of the proposed and pending
changes for in-memory database / storage support:
https://issues.apache.org/jira/browse/DERBY-646
Check the very first comments as a possible way.
Btw, you might want to create a new JIRA entry (if none already exists) for
t
By checking the README.htm provided in the SVN testing directory, I
can see there is a "storeall" testing suite which seems to test the
storage area.
Now, given I'm working on a new StorageFactory implementation, I
would like to know 2 things:
A) How can I enable my storageFactory as defa
