[ http://issues.apache.org/jira/browse/DERBY-1390?page=comments#action_12415403 ]
Rick Hillegas commented on DERBY-1390: -------------------------------------- Lance Andersen clarifies: Hi Rick, I never said non-compliance. As long as the method can be executed, what if anything you do with the method is up to you. We do not explicitly require that you must be able to disable the escape processing, just that the method executes successfully for compatibility purposes regards lance > Statement.setEscapeProcessing() is a NOP in Derby. > -------------------------------------------------- > > Key: DERBY-1390 > URL: http://issues.apache.org/jira/browse/DERBY-1390 > Project: Derby > Type: Improvement > Components: JDBC > Versions: 10.2.0.0 > Reporter: Rick Hillegas > Fix For: 10.2.0.0 > > This is a known issue with Derby and is documented in the Reference Guide. It > causes Derby to not be JDBC4 compliant. -- 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
