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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2013/06/25 07:08:21 UTC
[jira] [Updated] (DERBY-1742) SYSTEMALIAS column of type BOOLEAN in
SYS.SYSALIASES is created with the incorrect maximun length of 0
[ https://issues.apache.org/jira/browse/DERBY-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor updated DERBY-1742:
-----------------------------------
Labels: derby_triage10_11 (was: )
> SYSTEMALIAS column of type BOOLEAN in SYS.SYSALIASES is created with the incorrect maximun length of 0
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1742
> URL: https://issues.apache.org/jira/browse/DERBY-1742
> Project: Derby
> Issue Type: Task
> Components: SQL
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1
> Reporter: Daniel John Debrunner
> Priority: Trivial
> Labels: derby_triage10_11
>
> Boolean type's correct maximum width is 1.
> Seen by the COLUMN_SIZE column from DatabaseMetaData.getColumns returning 0 instead of 1.
> Caused by passing a 0 instead of a 1 in SYSAliasesRowFactory, will be fixed by DERBY-1734, which stops
> code like this passing in information that is redundant (and hence a chance for it to be wrong).
> Don't believe ir has any affect on the runtime behaviour of the system, adding this issue to investigate if an upgrade fix is required
> or just leave it at the wrong value for old databases.
--
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