[
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674300#action_12674300
]
Kristian Waagan commented on DERBY-646:
---------------------------------------
Thank you for the feedback, David.
> For what it's worth, in my situation, the option of having absolutely nothing
> written to disk is a huge benefit.
What do you want to happen with derby.log, which may contain critical
information about errors happening in Derby?
Note that the file by default will be overwritten when you restart Derby, so it
shouldn't eat up your disk space. Since very little is written to it under
normal operation, it shouldn't degrade performance. If you fire up lots of
instances in different directories (without setting derby.system.home), you do
get 'derby.log' files lying around though.
If you want to discard the information, I think you have the possibility to do
that yourself using one of the derby.stream.error properties. To make it even
easier, we could add a stream class to the Derby engine jar file that simply
discards the information (if specifying null causes the information to be
printed to std err).
My personal choice would be to not discard error information by default though,
and I think it should be a conscientious choice made by the user / developer,
but feel free to disagree :)
> 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, 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.
