[
https://issues.apache.org/jira/browse/DERBY-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-6129:
-----------------------------
Attachment: systables.txt
Whew, there are a few more errors in addition to the one you noticed -- all
having to do with the nullability column. The attached file containing the
query result has a double asterisk in the first column for the other
discrepancies.
I had to modify the query a bit to get all the output into the third column.
I'll file a patch.
> Reference Manual gives incorrect datatype for SYSCOLUMNS.COLUMNNAME
> -------------------------------------------------------------------
>
> Key: DERBY-6129
> URL: https://issues.apache.org/jira/browse/DERBY-6129
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: systables.txt
>
>
> The Reference Manual says that SYSCOLUMNS.COLUMNNAME has datatype CHAR(128).
> It's actual datatype is VARCHAR(128). It's probably worth running the
> following script to confirm the datatypes of all catalog columns described by
> the Reference Manual:
> connect 'jdbc:derby:memory:db;create=true';
> select cast(t.tablename as varchar( 20 )), cast(c.columnname as varchar(20)),
> c.columndatatype
> from sys.syscolumns c, sys.systables t
> where t.tablename like 'SYS%'
> and t.tableid = c.referenceid
> order by t.tablename, c.columnname;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
