Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

release-23.1: sql: alter sequence options no min, no max and as type to replicate postgreSQL #121307

Merged
merged 1 commit into from
Mar 29, 2024
Merged

release-23.1: sql: alter sequence options no min, no max and as type to replicate postgreSQL #121307

merged 1 commit into from
Mar 29, 2024

Commits on Mar 13, 2024

  1. fix: sequence no min, no max, change type to replicate postgresql 

    This commit changes 'NO MINVALUE' and 'NO MAXVALUE' sequence options
to replicate postgreSQL behavior.
If the sequence is ascending then the NO MAXVALUE is the largest value
for it int type and NO MINVALUE is 1.
If the sequence is descending then the NO MAXVALUE is -1 and NO MINVALUE
is the smallest value for its int type.
This commit also addresses how MINVALUE and MAXVALUE are automatically
changed when altering the seq int type. If either is equal to the
current types limit, then it is will automatically adjsut to the
changes types limits. Otherwise it will not change.

Release note (bug fix): Sequence options for 'NO MINVALUE' and 'NO
MAXVALUE' now replicate postgreSQL.

Sequence MINVALUE and MAXVALUE automatical adjust to new types bounds
mirroring behavior of postgreSQL.
    @andrew-delph
    andrew-delph committed Mar 13, 2024
    Configuration menu
    Copy the full SHA
    4194765 View commit details
    Browse the repository at this point in the history