[
https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729545#action_12729545
]
V.Narayanan commented on DERBY-3541:
------------------------------------
Oystein says:
"2. Somehow fix the case with authentication so that the database is shut down.
(I am not sure how)"
Although he does mean that it is difficult to shutdown the database when
authentication is enabled
(the same way shutdown is done when authentication is not enabled) he does not
mean this is not
a bug.
Like in my comments before, ij is a generic jdbc front end tool, I am not happy
with a derby specific
call here at all. Ideally speaking you should be capable of using ij with any
DB that supports a jdbc
driver.
If everyone agrees we can probably document that we need to shutdown DB's
before quitting and
prevent ij from going down without closing the DB's. That would be one probable
solution. But again
I am not sure I will be happy with such a crude fix.
Here is my 2 paisa :)
(IJ is a simple and elegant tool. There is a innocent simplicity to the tool
that I would never want it
to lose. If a user wants a sophisticated front end there are other options. We
should not clutter ij
unnecessarily.)
> quit; on ij with authentication enabled does not shutdown the derby modules
> that are loaded
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-3541
> URL: https://issues.apache.org/jira/browse/DERBY-3541
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.4.1.3
> Reporter: V.Narayanan
> Priority: Minor
> Attachments: derby.properties, PrintStackTrace.diff,
> WithoutAuthentication_StackTrace.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
