I don't know where all the bodies are buried. I started to look into
this and I have attached my preliminary code to bug 887. By applying the
datatype changes to a clean client and then running derbyall you will
get some idea. One place where we rely on these illegal casts is in the
ODBC metadata queries created by
java/build/org/apache/derbyBuild/ODBCMetadataGenerator. Those generated
queries rely on illegal casts from BOOLEAN to SMALLINT. My comments on
bug 887 address this issue.
Regards,
-Rick
Daniel John Debrunner wrote:
Rick Hillegas (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12366414 ]
Rick Hillegas commented on DERBY-499:
-------------------------------------
Let me punch up the importance of this point:
Our own production code already relies on pre-existing illegal
casts and comparisons. Quite likely, some of our customers do too.
Could you give examples how how this code depends on these casts and
comparisions? Maybe SQL queries, not sure what boolean expressions you
would be going against. Hard to see what the impact would be unless we
have concrete examples.
Thanks,
Dan.
