[jira] [Commented] (DERBY-5276) Reference manual has wrong length for BIGINT columns in system tables
[ https://issues.apache.org/jira/browse/DERBY-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079941#comment-13079941 ] Rick Hillegas commented on DERBY-5276: -- Hi Jayaram, To avoid the out of memory error, see item 4 in the instructions at http://db.apache.org/derby/manuals/dita.html#Setting+up+your+environment . I find that I am able to build the documentation when I set export ANT_OPTS="-Xmx512m" Hope this helps, -Rick > 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 > Attachments: derby5276-ref.diff > > > 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
[jira] [Commented] (DERBY-5276) Reference manual has wrong length for BIGINT columns in system tables
[ https://issues.apache.org/jira/browse/DERBY-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079762#comment-13079762 ] Jayaram Subramanian commented on DERBY-5276: Attaching the patch with modified dita files. When i tried to generate the html output i got a out of memory error because of which i was not able to test the final output. BUILD FAILED C:\derby-documentation\trunk\build.xml:108: The following error occurred while e xecuting this line: C:\derby-documentation\trunk\build.xml:146: The following error occurred while e xecuting this line: C:\derby-documentation\trunk\DITA-OT1.1.2.1\pretargets.xml:100: java.lang.OutOfM emoryError: Java heap space > 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 > Attachments: derby5276-ref.diff > > > 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
Re: [jira] [Commented] (DERBY-5276) Reference manual has wrong length for BIGINT columns in system tables
Jayaram Subramanian writes:
> Hi All,
> The dita configuration link in derby mention about updating config
> file in subversion with dita file... But i am not able to find the
> config file for subversion in my local pc... could you help me in
> identifying the locatio of the file.
I think that step is only needed to get the correct svn:eol-style
automatically if you add new dita files. So it shouldn't be required for
DERBY-5276, which only modifies existing files.
The configuration file is usually located at ~/.subversion/config. I
don't know about Windows, but it's suggested at
http://www.apache.org/dev/svn-eol-style.txt that it might be found at
the following location:
C:\Documents and Settings\{username}\Application Data\Subversion\config
--
Knut Anders
Re: [jira] [Commented] (DERBY-5276) Reference manual has wrong length for BIGINT columns in system tables
Hi All, The dita configuration link in derby mention about updating config file in subversion with dita file... But i am not able to find the config file for subversion in my local pc... could you help me in identifying the locatio of the file. With Regards jayaram On Thu, Jul 7, 2011 at 11:27 AM, Rick Hillegas (JIRA) wrote: > >[ > https://issues.apache.org/jira/browse/DERBY-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061416#comment-13061416] > > Rick Hillegas commented on DERBY-5276: > -- > > I vote for consistency: bump all of the BIGINT lengths to 20. Certainly the > SYSSEQUENCES columns can hold negative BIGINTs. For numeric columns in the > catalogs, length seems to refer to the max number of characters needed to > display the column value. > > > 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 > >Priority: Minor > > > > 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 > > >
[jira] [Commented] (DERBY-5276) Reference manual has wrong length for BIGINT columns in system tables
[ https://issues.apache.org/jira/browse/DERBY-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061416#comment-13061416 ] Rick Hillegas commented on DERBY-5276: -- I vote for consistency: bump all of the BIGINT lengths to 20. Certainly the SYSSEQUENCES columns can hold negative BIGINTs. For numeric columns in the catalogs, length seems to refer to the max number of characters needed to display the column value. > 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 >Priority: Minor > > 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
[jira] [Commented] (DERBY-5276) Reference manual has wrong length for BIGINT columns in system tables
[ https://issues.apache.org/jira/browse/DERBY-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059918#comment-13059918 ] Kim Haase commented on DERBY-5276: -- To work on a documentation issue, follow the instructions in http://db.apache.org/derby/manuals/dita.html. (Note: the correct toolkit version is a bit hard to find now -- you might have to Google for it.) The review and commit mechanism is similar to the one for code. For examples, look at some recently resolved documentation issues such as https://issues.apache.org/jira/browse/DERBY-5226 and https://issues.apache.org/jira/browse/DERBY-5212. Feel free to ask if you have any questions. We welcome your help! > 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 >Priority: Minor > > 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
[jira] [Commented] (DERBY-5276) Reference manual has wrong length for BIGINT columns in system tables
[ https://issues.apache.org/jira/browse/DERBY-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059668#comment-13059668 ] Jayaram Subramanian commented on DERBY-5276: Hi Knut I would like to take up this reference manual updation. Please let me know on how to proceed. > 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 >Priority: Minor > > 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
