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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2009/03/13 11:47:50 UTC
[jira] Updated: (DERBY-4084) Determine the subSubProtocol name for
the in-memory back end
[ https://issues.apache.org/jira/browse/DERBY-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4084:
-----------------------------------
Attachment: derby-4084-1a-subSubProtocol_name.diff
Patch 1a changes the subSubProtocol name to 'memory'.
A typical connection JDBC URL (for the embedded driver) will then be 'jdbc:derby:memory:wombatDb'.
> 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
> Attachments: derby-4084-1a-subSubProtocol_name.diff
>
>
> 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.