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

fix!: EXPOSED-536 Short column allows out-of-range values #2231

Merged
merged 1 commit into from
Sep 10, 2024
Merged

fix!: EXPOSED-536 Short column allows out-of-range values #2231

merged 1 commit into from
Sep 10, 2024

Commits on Sep 10, 2024

  1. fix!: EXPOSED-536 Short column allows out-of-range values 

    For Oracle, Short data type was changed from SMALLINT to NUMBER(5) because SMALLINT is stored as NUMBER(38) in the database and takes up unnecessary storage. Another reason is that this is a precursor to the column type change detection feature for migration, where it will be useful to have the column type be more specific than NUMBER(38).

A check constraint was added to ensure that no out-of-range values are stored.
    @joc-a
    joc-a committed Sep 10, 2024
    Configuration menu
    Copy the full SHA
    ef3c88c View commit details
    Browse the repository at this point in the history