[
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-646:
-------------------------------------
Fix Version/s: (was: 10.5.0.0)
Following Kathey's recommendation, taking off fix in 10.5 - so this won't be in
the 10.5 fixed bugs list. It's still on the list of new functionality. We need
to somehow point out that this is the first stage, though. Is it ok to say it's
'experimental' or is that too scary?
> 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
> Affects Versions: 10.5.0.0
> 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-3a-jmx_experiment.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.
