You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jean T. Anderson (JIRA)" <de...@db.apache.org> on 2006/02/08 04:15:59 UTC
[jira] Resolved: (DERBY-570) wrong java.sql.Type id implied for
LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ]
Jean T. Anderson resolved DERBY-570:
------------------------------------
Fix Version: 10.2.0.0
Resolution: Fixed
Committed Eric Radzinski's derby570-3.diff patch to the trunk, revision 375836. Modified files:
$ svn status
M src/ref/rrefsqlj30118.dita
> 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