db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francois Orsini (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-646) In-memory backend storage support
Date Wed, 11 Mar 2009 19:51:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681006#action_12681006
] 

Francois Orsini commented on DERBY-646:
---------------------------------------

+1. Having these (hooks) even as an experiment could be very useful while the in-memory feature
is being tested.

I would probably wait after 10.5 because allowing for database deletion, but that is just
me - just because there needs probably more time to investigate it and its possible side effects.

Maybe worth re-enforcing somewhere (notes if any) that the database is locked and its activity
blocked while its estimated space usage is computed.

> 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
>             Fix For: 10.5.0.0
>
>         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.


Mime
View raw message