[
https://issues.apache.org/jira/browse/DERBY-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468656
]
Knut Anders Hatlen commented on DERBY-2258:
-------------------------------------------
I think DATA_TYPE should be 2009 (java.sql.Types.SQLXML). Not sure about
LITERAL_PREFIX and LITERAL_SUFFIX, but I think they should be NULL. I'm also
not sure about CREATE_PARAMS, but suspect it should be NULL as well.
UNSIGNED_ATTRIBUTE and AUTO_INCREMENT should probably be false instead of null.
LOCAL_TYPE_NAME is identical to TYPE_NAME (not null) for the other types, but
that seems to be how your patch implements it too. (You probably got confused
by the query in metadata.properties. The VALUES clause has 15 columns, but the
top-level SELECT inserts three extra columns at position 13, 16 and 17.)
> DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types
> correctly.
> ---------------------------------------------------------------------------------
>
> Key: DERBY-2258
> URL: https://issues.apache.org/jira/browse/DERBY-2258
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0,
> 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Saurabh Vyas
> Priority: Minor
> Attachments: Derby-2258.diff, Derby-2258.stat
>
>
> These types are returned but not supported by Derby.
> LONG NVARCHAR
> NATIONAL CHAR
> NATIONAL CHAR VARYING
> The XML type is supported by Derby but not returned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
