DatabaseSchema isCompatibleSubset looks for incorrect procedure key
-------------------------------------------------------------------
Key: SEQUOIA-1028
URL: https://forge.continuent.org/jira/browse/SEQUOIA-1028
Project: Sequoia
Type: Bug
Components: Core
Versions: Sequoia 2.10.8
Environment: embedded Derby
embedded sequoia
Reporter: Chris Ekberg
Priority: Minor
When checking to see whether a schema is compatible, DatabaseSchema's
isCompatibleSubset calls other.getProcedure(String) with procedure.getName()
instead of procedure.getKey().
With Derby, the "name" and "key" appear to not be the same due to parentheses
after the name, so no match is found and the schema are always considered
incompatible.
Changing to other.getProcedure(procedure.getKey() ) fixes this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
