You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "James Synge (JIRA)" <de...@db.apache.org> on 2006/03/09 19:38:39 UTC
[jira] Commented: (DERBY-646) In-memory backend storage support
[ http://issues.apache.org/jira/browse/DERBY-646?page=comments#action_12369704 ]
James Synge commented on DERBY-646:
-----------------------------------
I'm with Mike in wanting to use this for unit testing purposes. My group has a "fake" db implementation that provides an in-memory "database" (not sql), but it is becoming a pain to maintain it as we try to take more advantage of SQL features, so Stephen's solution sounds great.
> 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
Re: [jira] Commented: (DERBY-646) In-memory backend storage support
Posted by Mike Matrigali <mi...@sbcglobal.net>.
In the meantime you should try out the current system using the
durability=test flag, for your unit testing needs. It was implemented
specifically for this application from other user requests. It does
no sychronous I/O so effectively uses the OS's memory cache.
James Synge (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/DERBY-646?page=comments#action_12369704 ]
>
> James Synge commented on DERBY-646:
> -----------------------------------
>
> I'm with Mike in wanting to use this for unit testing purposes. My group has a "fake" db implementation that provides an in-memory "database" (not sql), but it is becoming a pain to maintain it as we try to take more advantage of SQL features, so Stephen's solution sounds great.
>
>
>
>>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.
>
>