You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This sounds like an edge case that is unlikely to ever be relevant in real usage. Or to phrase differently, limiting the increment to an INT (or even a SMALLINT) should be sufficient for normal usage. There is no reason to extend it to a BIGINT.
Submitted by: @pavel-zotov
recreate table test0( id bigint generated by default as identity (start with 9223372036854775807 increment by -2147483647) );
recreate table test0( id bigint generated by default as identity (start with 9223372036854775807 increment by -2147483648) );
recreate table test0( id bigint generated by default as identity (start with 9223372036854775807 increment by -2147483649) );
Second and third statements fail with:
Statement failed, SQLSTATE = 42000
Dynamic SQL Error
-SQL error code = -104
-Token unknown - line 1, column 113
-2147483648 (-21474836489)
Checked on 4.0.0.2104
The text was updated successfully, but these errors were encountered: