[DERBY-4171] Connections to on-disk db go to in-memory db if in-memory db with same name is booted

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.5.1.1, 10.6.1.0
• Fix Version/s: 10.5.2.0, 10.6.1.0
• Component/s: Store
• Assignee: Kristian Waagan
• Reporter: Knut Anders Hatlen
• Created: 20/Apr/09 13:17
• Updated: 02/Feb/10 10:03
• Resolved: 18/Jun/09 12:53

Description

When an in-memory database has been booted, subsequent attempts to connect to an ordinary (on-disk) database with the same name as the in-memory database will connect to the in-memory db.

ij version 10.5
ij> connect 'jdbc:derby:memory:MyDB;create=true'; – with subprotocol memory
ij> create table t (x varchar(30));
0 rows inserted/updated/deleted
ij> insert into t values 'This is the in-memory backend';
1 row inserted/updated/deleted
ij> connect 'jdbc:derby:MyDB;create=true'; --without subprotocol memory, should create disk db
WARNING 01J01: Database 'MyDB' not created, connection made to existing database instead.
ij(CONNECTION1)> select * from t;
X
------------------------------
This is the in-memory backend

1 row selected

Issue Links

• relates to: DERBY-4271 testBootSameDbDifferentSubSubProtocol(org.apache.derbyTesting.functionTests.tests.memorydb.BasicInMemoryDbTest)java.sql.SQLException: Database 'BSDDSSP' not found.