[
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-646:
----------------------------------
Attachment: derby-646-2b-vfmem_first_rev.diff
Committed patch 'derby-646-2b-vfmem_first_rev.diff' to trunk with revision
752114.
I expect more work will be done under various sub-tasks of this issue.
It would be nice to get early feedback from users and developers willing to try
out the feature under development.
Note that I have set the subSubProtocol to be 'in-memory' based on the feedback
on DERBY-4084, but this may change.
The in-memory back end is working in my environment, but there may be problems
on other platforms. For instance, is the case-insensitive mode of Windows a
problem?
> In-memory backend storage support
> ---------------------------------
>
> Key: DERBY-646
> URL: https://issues.apache.org/jira/browse/DERBY-646
> Project: Derby
> Issue Type: New Feature
> Components: Store
> Environment: All
> Reporter: Stephen Fitch
> Assignee: Kristian Waagan
> Attachments: derby-646-1a-raw-compiles.diff,
> derby-646-1a-raw-compiles.stat, derby-646-20090222.diff,
> derby-646-20090222.stat, derby-646-2a-vfmem_first_rev.diff,
> derby-646-2a-vfmem_first_rev.stat, derby-646-2b-vfmem_first_rev.diff,
> derby-646-performance_comparison_1a.txt, svn.diff
>
>
> To allow creation and modification of databases in-memory without requiring
> disk access or space to store the database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
