[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Jean T. Anderson closed DERBY-570: ----------------------------------
No problems have been reported with the patch that was committed, so closing. > wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA > ------------------------------------------------------------ > > Key: DERBY-570 > URL: http://issues.apache.org/jira/browse/DERBY-570 > Project: Derby > Type: Bug > Components: Documentation > Versions: 10.1.1.0 > Reporter: Rick Hillegas > Fix For: 10.2.0.0 > Attachments: derby570-2.diff, derby570-3.diff, derby570.diff, > rrefsqlj30118.html > > The Datatypes section of the Reference Manual says that LONG VARCHAR FOR BIT > DATA is identical to VARCHAR FOR BIT DATA but does not give a jdbc type, > implying that LONG VARCHAR FOR BIT DATA has the same jdbc type as VARCHAR FOR > BIT DATA, i.e., VARBINARY. This section should say that LONG VARCHAR FOR BIT > DATA has the following jdbc type: LONGVARBINARY. -- 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
