[
https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673850#action_12673850
]
Cheng Che Chen commented on DERBY-646:
--------------------------------------
Hi folks,
I've implemented the interfaces
org.apache.derby.io.{StorageFile,StorageRandomAccessFile,WritableStorageFactory}
such that all file system operations are emulated entirely in memory,
producing no file or directory on disk. I'm more than happy to contribute the
implementation.
However, I have a build problem for which I hope to get some help. To start,
for simplicity, I added my source files to
"trunk/java/engine/org/apache/derby/impl/io" -- so that I didn't have to
create/modify any "build.xml" files. I then tried to build the sources and the
JAR files. The sources built with no problem -- all of my classes appeared in
"trunk/classes/org/apache/derby/impl/io". However, for some reason, the JAR
build process did not put my classes into "derby.jar". As a result, I had to
set the JAVA class path to "trunk/classes" during testing.
I'd appreciate any help resolving this build problem.
Thanks.
> 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.
