[
https://issues.apache.org/jira/browse/DERBY-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680191#action_12680191
]
Rick Hillegas commented on DERBY-4084:
--------------------------------------
Our other subprotocols seem to be descriptive (e.g., "directory", "classpath",
"jar") so I vote for another descriptive name. I think that "memory" is fine.
Bryan raises the issue of how we distinguish the transient in-memory database
(implemented by Kristian's patch) from Cheng's implementation, which snapshots
the database to disk on exit. Initially, I thought that the subprotocol would
be a reasonable place to make this distinction. However, maybe it would be
better to distinguish the two behaviors with other attributes on the connection
URL. For instance, we could introduce two new attributes:
loadFrom=blahblahblah
saveOnExit=blahblahblah
> Determine the subSubProtocol name for the in-memory back end
> ------------------------------------------------------------
>
> Key: DERBY-4084
> URL: https://issues.apache.org/jira/browse/DERBY-4084
> Project: Derby
> Issue Type: Sub-task
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
>
> The community should agree on a name for the subSubProtocol for the in-memory
> back end. The name will be used in the connection URL, and it is the
> mechanism used to tell Derby to use the in-memory back end:
> jdbc:derby:subSubProtocol:dbName
> Two hot candidates are:
> o mem
> o memory
> The former is shorter, the latter is slightly more descriptive. If you have
> opinions on this, please post a comment.
> We should decide on this before we cut the branch for 10.5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
