[DERBY-646] In-memory backend storage support

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.5.1.1
• Fix Version/s: 10.5.1.1
• Component/s: Store
• Environment: All
• Assignee: Kristian Waagan
• Reporter: Stephen Fitch
• Created: 26/Oct/05 02:32
• Updated: 07/May/10 09:05
• Resolved: 07/May/10 09:05

Description

To allow creation and modification of databases in-memory without requiring disk access or space to store the database.

Issue Links

• relates to: DERBY-4581 databaseName attribute needs to include subsubprotocol, if there is one
• relates to: DERBY-2798 A new approach for main-memory database
• relates to: DERBY-4525 Document the in-memory storage back end

Sub-Tasks

• Determine the subSubProtocol name for the in-memory back end: Closed
• Improve testing of the in-memory back end: Closed
• Improve handling of the database temporary directory: Closed
• Enforce absolute paths in the in-memory back end internal storage structure: Closed
• Allow unlimited growth for in-memory conglomerates: Closed