[
https://issues.jboss.org/browse/TEIID-2061?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2061.
-----------------------------------
Resolution: Done
Added the system property org.teiid.comparableObject to allow columns typed as object to
be comparable. The instance objects are expected to extend java.lang.Comparable. A
workaround for objects that do not implement comparable would be to add a wrapping type
that compares based upon hashcode. Teiid does provide a facility to automatically do
that.
It is still desirable to have an extensible type system, which could metadata drive the
comparability, but for now the type logic is static and spread out which makes an overhaul
difficult.
Allow for object type equality
------------------------------
Key: TEIID-2061
URL:
https://issues.jboss.org/browse/TEIID-2061
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Allowing for object type equality would allow for the use of object values as keys.
Allowing for full comparability could be done as well, but would result in runtime errors
if mixed values are used or if the type is not comparable.
Note that we could alternatively choose to represent object values as their serialized
byte[] values, in which case compatibility is implied. However that is still not the
natural compare ordering nor does it account for method based equality vs. identical
serialized bytes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira