db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashwin Jayaprakash (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-646) In-memory backend storage support
Date Fri, 20 Jul 2007 16:44:07 GMT

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

Ashwin Jayaprakash commented on DERBY-646:
------------------------------------------

The Derby JAR file is sealed - and this means that all the Derby packages specified in the
JAR file's Manifest are sealed and you cannot add a new Class that shares the Package names
to the Classpath. 

Since there are classes in org.apache.derby.impl.io Package in the Derby "sealed" JAR, you
cannot append a Class like org.apache.derby.impl.io.PureMemStore that resides outside the
JAR to the ClassPath. Unless I'm completely wrong, you will have to use the Source code and
add your files there and then recreate the JAR file.

> 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.


Mime
View raw message