Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Duplicate
-
10.6.1.0
-
None
-
None
Description
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?
Attachments
Issue Links
- is duplicated by
-
DERBY-4525 Document the in-memory storage back end
- Closed
- is related to
-
DERBY-646 In-memory backend storage support
- Closed