[
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674134#action_12674134
]
Kristian Waagan commented on DERBY-646:
---------------------------------------
Cheng,
As it happens, I have a working prototype as well. It closely follows the
approach taken by Stephen Fitch in the original patch.
If possible, I think we should somehow try to coordinate our work. I'd like to
spend a few more days cleaning up the initial code contribution, as it is
pretty fresh.
Regarding testing, the easiest way to do it is to override the storage factory
for PersistentService.DIRECTORY in BaseMonitor. Then you can just run the tests
as normal, either by using JUnit directly or by running ant junitreport.
Currently, I'm getting 24 failures and 66 errors when running junitreport.
Somes of these are to be expected, as some tests explicitly tries to access
files in the database directory. I also note problems in general with
encryption, backup and restoreFrom (in the url) etc, but I suspect these tests
require the database files to exist as well.
Also, some tests will just fail because all the data is stored in memory, for
instance 'ant junit-lowmem'.
Lastly, the test framework has a decorator to delete a database and/or a
directory. Since it is working against the file system only, it doesn't manage
to delete an in-memory database.
Note that bugs in the prototype tend to hide if they are triggered during boot.
If things go wrong, I recommend to check derby.log before starting debugging.
I'll post my code (and the test results) in a day or two, and we should
consider how to best cooperate on this issue.
Regards,
> 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.
