[ http://issues.apache.org/jira/browse/DERBY-586?page=comments#action_12362103 ]
Cherry Development commented on DERBY-586: ------------------------------------------ I agree that this is a problem. It's especially problematic when a derby jdbc connection is being provided to an application by the container. It also makes things difficult when you're using hibernate, since the application is similarly isolated from details of the database. I have two possible suggestions: First suggestion: A new jdbc connection parameter, connectionShutdown. When set to true, the derby system will be automatically shut down when the last connection to that database is closed. Second suggestion: A new jdbc connection parameter, jvmShutdown. When set to true, derby will automatically register a shutdown handler with the Runtime that will shut down derby. > Provide an alternative means to shut down a database other than using > getConnection() > -------------------------------------------------------------------------------------- > > Key: DERBY-586 > URL: http://issues.apache.org/jira/browse/DERBY-586 > Project: Derby > Type: New Feature > Components: Services > Reporter: Lance Andersen > Priority: Minor > > It would be nice to provide an alternative mechanism to shutdown a database > other than calling getConnection() and having an Exception thrown. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
