db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-5276) Reference manual has wrong length for BIGINT columns in system tables
Date Fri, 05 Aug 2011 16:17:27 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase resolved DERBY-5276.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
                      10.8.1.6
    Issue & fix info:   (was: [Patch Available])

Committed patch derby5276-ref.diff to documentation trunk at revision 1154270. 
Merged to 10.8 doc branch at revision 1154287.

> Reference manual has wrong length for BIGINT columns in system tables
> ---------------------------------------------------------------------
>
>                 Key: DERBY-5276
>                 URL: https://issues.apache.org/jira/browse/DERBY-5276
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Jayaram Subramanian
>            Priority: Minor
>             Fix For: 10.8.1.6, 10.9.0.0
>
>         Attachments: derby5276-ref.diff, derby5276.stat, derby5276.zip
>
>
> The description of the SYSCOLUMNS table at http://db.apache.org/derby/docs/dev/ref/rrefsistabs22441.html
says that the BIGINT columns AUTOINCREMENTVALUE, AUTOINCREMENTSTART and AUTOINCREMENTINC have
length 19. The maximum length of a BIGINT is 20 (when including the sign for negative values).
Here's an example that shows that these columns can hold values whose length is 20:
> ij> create table t(x bigint not null generated always as identity (start with -1234567890123456789,
increment by -1234567890123456789));
> 0 rows inserted/updated/deleted
> ij> select autoincrementvalue, autoincrementstart, autoincrementinc from sys.syscolumns
where columnname='X';
> AUTOINCREMENTVALUE  |AUTOINCREMENTSTART  |AUTOINCREMENTINC    
> --------------------------------------------------------------
> -1234567890123456789|-1234567890123456789|-1234567890123456789
> 1 row selected
> Other places where BIGINT columns are listed with length 19:
> SYSCONGLOMERATES - http://db.apache.org/derby/docs/dev/ref/rrefsistabs39391.html
> SYSFILES - http://db.apache.org/derby/docs/dev/ref/rrefsistabs40972.html
> SYSSEQUENCES - http://db.apache.org/derby/docs/dev/ref/rrefsistabssyssequences.html
> SYSXPLAIN_RESULTSET_TIMINGS - http://db.apache.org/derby/docs/dev/ref/rrefsysxplain_resultset_timings.html
> SYSXPLAIN_STATEMENT_TIMINGS - http://db.apache.org/derby/docs/dev/ref/rrefsysxplain_statement_timings.html
> SYSCS_DIAG.SPACE_TABLE - http://db.apache.org/derby/docs/dev/ref/rrefsyscsdiagtables.html
> I haven't verified if negative values are allowed in all of these columns. If they are
only allowed to hold non-negative values, should we keep the value 19? Or should we change
all to 20 for consistency? I'm assuming that "length" in these tables refers to the display
size of the columns.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message