[
https://issues.apache.org/jira/browse/DERBY-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048790#comment-13048790
]
Tony Brusseau edited comment on DERBY-5274 at 6/13/11 9:28 PM:
---------------------------------------------------------------
This works:
CREATE TABLE kb.term (
term_id BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH
999999999999)
);
This fails (silently):
CREATE TABLE kb.term (
term_id BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH
1000000000000)
);
Looks like 1 trillion is the magic cutoff where it stops working.
was (Author: apb):
This works:
CREATE TABLE kb.term (
term_id BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH
999999999999)
);
This fails:
CREATE TABLE kb.term (
term_id BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH
1000000000000)
);
Looks like 1 trillion is the magic cutoff where it stops working.
> Cannot create tables correctly with auto generated identity columns that
> start with large numbers
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-5274
> URL: https://issues.apache.org/jira/browse/DERBY-5274
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.1
> Environment: Linux 10.3.
> Reporter: Tony Brusseau
> Priority: Blocker
>
> CREATE TABLE kb.constant_term
> (
> term_id BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY
> (START WITH 648518346341351400, INCREMENT BY 1),
> constant_name VARCHAR(1024) NOT NULL
> );
> The above SQL causes the table to be created but no columns to be defined (no
> error message is reported). If I change 648518346341351400 to a 0, then the
> table is created normally with all the columns defined correctly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
