db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4428) Add proper delete mechanism for in-memory databases
Date Thu, 29 Oct 2009 15:53:59 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771455#action_12771455
] 

Dag H. Wanvik commented on DERBY-4428:
--------------------------------------

SQL uses the keyword "DROP", is there a reason you prefer "delete" over drop in the URL?

> authorization (currently it checks if the user is the database owner
> if authentication is on, doesn't require SQL authorization to be
> on).

Database shutdown is restricted to DBO when authentication AND
authorization are both enabled; I think because it was felt that doing
it for authentication only could cause problems for existing
apps. Since thre is no prior use here, that would not be a
problem. But it would be slightly asymmetrical. What do you think?

The system privileges work was intended to control who can create
databases and would probably be required for dropping (deletion), at
least if we enable it for on-disk databases. But since that work is still
pending, I think limiting this to DBO is a good choice.

I think enabling dropping of on-disk databases is interesting. What would the cons be?



> Add proper delete mechanism for in-memory databases
> ---------------------------------------------------
>
>                 Key: DERBY-4428
>                 URL: https://issues.apache.org/jira/browse/DERBY-4428
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Services, Store
>    Affects Versions: 10.6.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-4428-0a-preview_patch.diff
>
>
> The current mechanism for deleting in-memory databases isn't good enough, and a proper
one must be added.
> It is also important to be able to delete in-memory databases, since they occupy valuable
main memory that should be discarded when the database is no longer needed.
> I intend to implement the mechanism by using the JDBC connection URL:
> "jdbc:derby:memory:myDatabase;delete=true[;user=X;password=Y]
> The connection attempt will throw an exception in any case, either because the request
failed or because it succeeded.
> Reasons for a failure can be invalid user and/or password, lacking encryption attributes,
or conflicting attributes.
> For the time being, only the database owner will be allowed to delete databases (*note*:
do we have a way to control/limit in-memory database creation?)

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