[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12441374 ] Knut Anders Hatlen commented on DERBY-1610: -------------------------------------------
Thanks Tomohito. If the methods are static, each setter method must call getColumnMetaDataX(), getColumnType() and checkForEscapedCallWithResult(). I think it is better to have these calls in checkTypeForXXX() because it makes the setters cleaner and reduces the footprint. Since it reduces the amount of duplicated code, I think it also makes the code more maintainable. > 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-jdk16.diff, DERBY-1610.diff, > DERBY-1610_2.diff, DERBY-1610_3.diff, DERBY-1610_4.diff, DERBY-1610_5.diff, > DERBY-1610_6.patch, DERBY-1610_7.patch, DERBY-1610_7_regressionfix.patch, > DERBY-1610_7_regressionfix_2.patch, DERBY-1610_7_regressionfix_2_2.patch, > DERBY-1610_7_regressionfix_2_3.patch, parameterMapping.diff, > parameterMapping.diff, > parameterMapping.diff.betweenEmbedded_and_NetworkServerNetworkClient, > parameterMapping.out.7.diff, parameterMapping.out.diff, > 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
