Setting the database class path takes effect for the current connection but not
others until a database reboot.
---------------------------------------------------------------------------------------------------------------
Key: DERBY-2035
URL: http://issues.apache.org/jira/browse/DERBY-2035
Project: Derby
Issue Type: Bug
Components: SQL
Affects Versions: 10.2.1.6
Reporter: Daniel John Debrunner
Priority: Minor
After setting the derby.database.classpath as a database property the current
connection sees its effects, such as being able to load classes from the jar
added into the class path. However a newly opened connection does not see its
effect. Shutting down and re-booting the database makes the change visible to
all.
The new test lang.DatabaseClassLoadingTest will have code that shows this bug
commented with this bug number.
--
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
