db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trejkaz (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-393) Allow multiple JVMs to have read-only access to the same directory-based database
Date Mon, 27 Jun 2005 05:45:00 GMT
     [ http://issues.apache.org/jira/browse/DERBY-393?page=all ]

Trejkaz updated DERBY-393:

    Attachment: readonly.patch

This patch creates a new URL sub-scheme "readonlydirectory" which can be used to load a database
from a directory in read-only mode.

It isn't ideal... for one, the URL syntax is a little unwieldy.  The syntax is currently like

I would rather the syntax be like this:

But I couldn't figure out how to do the latter.  My patch only contains the Java 1.4 version
of the read-only store.  For completeness, I suppose you'd need a 1.3 and a 1.4 version. 
Either that or a decorator class which wraps any other store.  I suppose that the decorator
approach would make re-use a little easier.

> Allow multiple JVMs to have read-only access to the same directory-based database
> ---------------------------------------------------------------------------------
>          Key: DERBY-393
>          URL: http://issues.apache.org/jira/browse/DERBY-393
>      Project: Derby
>         Type: New Feature
>   Components: Store
>     Reporter: Trejkaz
>  Attachments: readonly.patch
> For an application I'm building, we needed to permit multiple JVMs to access the same
> We couldn't easily use a network server configuration, as it would be difficult to figure
out who to connect to since either user might want to view the database while the other database
is offline.
> We couldn't just dump all the data in a JAR file, as our databases often end up being
several gigabytes in size.
> So what we really need is a version of the directory store which is treated as if it
were read-only.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message