db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Sims (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-646) In-memory backend storage support
Date Tue, 17 Feb 2009 19:55:00 GMT

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

David Sims commented on DERBY-646:

Thanks, Kristian.

In my situation, I would use Derby as a strictly embedded database, and I don't want my users
to even be confused by the presence of a derby.log file, however empty it may be. The experience
with my users tells me that it's best just to have absolutely nothing. I can deal with the
usual SQLException errors that come along.

However you and the others might feel that should best be configured in Derby, I leave up
to you all. I would just like to chime in and request that there be a way to configure things
so that absolutely nothing is on disk, including derby.log -- however that might work out.


> 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
>         Attachments: derby-646-1a-raw-compiles.diff, derby-646-1a-raw-compiles.stat,
> 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.

View raw message