[ http://issues.apache.org/jira/browse/DERBY-646?page=comments#action_12369719 ]
Daniel John Debrunner commented on DERBY-646: --------------------------------------------- I think it would be great to have an in-memory db support like this and thanks for working on it Stephen, but there are a few issues to resolve first. We would need an ICLA on file at apache from Stephen Fitch before this could be committed into Derby. A quick look at the patch showed a couple of extra classes in the org.apache.derby.io package which is the published api for the virtual file system, classes such as VirtualFileData and VirtualFS. I can't tell what the purpose of these classes are since there are no comments for them, thus it makes it impossible for anyone to implement them without guessing what the requirements are. Also seemed to be no tests provided with the patch, so how would a reviewer know that this works or not? Copyrights on all the files seem to have incorrect dates, and file names. The wiki has information on what is required: http://wiki.apache.org/db-derby/DerbyContributorChecklist http://wiki.apache.org/db-derby/DerbyCommitProcess http://wiki.apache.org/db-derby/PatchAdvice > In-memory backend storage support > --------------------------------- > > Key: DERBY-646 > URL: http://issues.apache.org/jira/browse/DERBY-646 > Project: Derby > Type: New Feature > Components: Store > Environment: All > Reporter: Stephen Fitch > Assignee: Stephen Fitch > Attachments: 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
