[jira] Commented: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded

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

Øystein Grøvlen commented on DERBY-3541:
----------------------------------------

I think it is unfortunate that ij behaves differently with and without authentication.

I also feel that is very convenient that ij shut down the database when I exit.  Lately, when I have done some work in ij on a database with authentication/authorization turned on, it has been very annoying that if I quit I ij after doing a large update operation, it has taken a long time to boot the database the next time.  (Now I understand why)

I see the following possible solutions:

1. Change ij so the database is never shut down on quit, not just when authentication is turned on.  Document that users need to shutdown databases before they exit ij, similarly to the message to JDBC programmers.
2. Somehow fix the case with authentication so that the database is shut down.  (I am not sure how)
3. Let quit report error if ij is not able to shut down a database due to authentication.  Introduce a new command that can be use to force quit ij without shutting down databases.




--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.