db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alistair Phipps (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-393) Allow multiple JVMs to have read-only access to the same directory-based database
Date Tue, 19 May 2009 20:03:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710853#action_12710853

Alistair Phipps commented on DERBY-393:

I solved the same issue by defining a subsubprotocol:

System.setProperty("derby.subSubProtocol.readOnly", "x.ReadOnlyDirStorageFactory");

package x;
public class ReadOnlyDirStorageFactory extends DirStorageFactory {
    public boolean isReadOnlyDatabase() {
        return true;

Unless I'm missing something, I think this issue can be closed.

> Allow multiple JVMs to have read-only access to the same directory-based database
> ---------------------------------------------------------------------------------
>                 Key: DERBY-393
>                 URL: https://issues.apache.org/jira/browse/DERBY-393
>             Project: Derby
>          Issue 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.
You can reply to this email to add a comment to the issue online.

View raw message