[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: rrefsqlj30118.html derby570-3.diff derby570-3.diff removes the compile time type section from the topic. Latest HTML file is included for review. > 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 > 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
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: (was: rrefsqlj30118.html) > 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 > Attachments: derby570-2.diff, derby570.diff > > 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
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: derby570-2.diff rrefsqlj30118.html The newest patch and HTML file address Dan's suggestion. I've reformatted the topic to match the other data type topics. Also, the suggested compile time to use was "byte [ ]" All the other data type topics used the fully-qualified name though, so I used java.lang.Byte. Let me know if that's not correct. > 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 > Attachments: derby570-2.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
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: (was: rrefsqlj30118.html) > 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 > Attachments: derby570.diff > > 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
[jira] Updated: (DERBY-570) wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ] Eric Radzinski updated DERBY-570: - Attachment: derby570.diff rrefsqlj30118.html The attached patch adds the requested line ot the LONG VARCHAR FOR BIT DATA topic. HTML file is included for review. > 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 > Attachments: 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
