db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4581) databaseName attribute doesn't seem to work with in-memory databases
Date Sat, 10 Apr 2010 21:55:43 GMT

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

Kristian Waagan commented on DERBY-4581:

This problem isn't limited to the in-memory protocol.
Derby simply removes the prefix 'jdbc:derby:' and checks if the remaining string (which may
be terminated/truncated by a semi colon character) has a length of zero. If so, it checks
the databaseName attribute.

Another workaround is to include the subsubprotocol in databaseName, i.e. "connect 'jdbc:derby:;databaseName=memory:myDB'".

> databaseName attribute doesn't seem to work with in-memory databases
> --------------------------------------------------------------------
>                 Key: DERBY-4581
>                 URL: https://issues.apache.org/jira/browse/DERBY-4581
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:
>            Reporter: Kim Haase
>            Priority: Minor
> In a recent build from the trunk, the databaseName attribute doesn't seem to work correctly
with an in-memory database. 
> When I'm in ij, I can create an in-memory db, disconnect, and then connect again, and
the db is still there. I can connect to it the usual way, but not using the databaseName attribute
-- I tried a couple of different ways:
> ij> connect 'jdbc:derby:memory:myDB;create=true';
> ij> create table t(c int);
> 0 rows inserted/updated/deleted
> ij> disconnect;
> ij> connect 'jdbc:derby:memory:myDB';
> ij> insert into t values(1), (2);
> 2 rows inserted/updated/deleted
> ij> select * from t;
> C
> -----------
> 1
> 2
> 2 rows selected
> ij> disconnect;
> ij> connect 'jdbc:derby:memory;databaseName=myDB';
> ERROR XJ004: Database 'memory' not found.
> ij> connect 'jdbc:derby:memory:;databaseName=myDB';
> ERROR XJ004: Database 'memory:' not found.
> The workaround is to use the simpler syntax 'jdbc:derby:memory:myDB', but the attribute
ought to work too, shouldn't it?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message