[
https://issues.apache.org/jira/browse/DERBY-4581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-4581:
-----------------------------
Component/s: (was: SQL)
Store
> 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: 10.6.0.0
> 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.
-
You can reply to this email to add a comment to the issue online.
