[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436122 ] Knut Anders Hatlen commented on DERBY-1610: -------------------------------------------
Although embedded throws XCL12 in some cases, I don't think the client driver needs to do the same. From the comments in parameterMapping, it seems like XCL12 was not meant to be used permanently. I think it would be better if the client consistently threw 22005 for all the type errors. The patch looks good. Perhaps you could add a comment describing the PossibleTypes class? > Resolve difference of type compatibility between Embedded and > NetworkServer/NetworkDriver > ----------------------------------------------------------------------------------------- > > Key: DERBY-1610 > URL: http://issues.apache.org/jira/browse/DERBY-1610 > Project: Derby > Issue Type: Bug > Components: Network Server, Network Client > Reporter: Tomohito Nakayama > Assigned To: Tomohito Nakayama > Attachments: DERBY-1610.diff, DERBY-1610_2.diff, DERBY-1610_3.diff, > DERBY-1610_4.diff, DERBY-1610_5.diff, parameterMapping.diff, > parameterMapping.diff, > parameterMapping.diff.betweenEmbedded_and_NetworkServerNetworkClient, > parameterMapping_3.diff, TestNullChar.java, TestTypeCompatibility.java, > XCL12.diff > > > There exists difference of type compatibility between Embedded and > NetworkServer/NetworkClient. > This issue tries to resolve it. -- 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
