-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
PostgreSQL: Doesn't support (n CHAR) syntax, but only (n) syntax. #4662
Comments
mkarg
added a commit
to mkarg/liquibase
that referenced
this issue
Aug 11, 2023
…but only (n) syntax.
3 tasks
filipelautert
pushed a commit
to mkarg/liquibase
that referenced
this issue
Aug 29, 2023
…but only (n) syntax.
filipelautert
pushed a commit
that referenced
this issue
Sep 1, 2023
filipelautert
pushed a commit
to mkarg/liquibase
that referenced
this issue
Sep 20, 2023
…but only (n) syntax.
filipelautert
pushed a commit
to mkarg/liquibase
that referenced
this issue
Sep 20, 2023
…but only (n) syntax.
filipelautert
pushed a commit
that referenced
this issue
Sep 20, 2023
filipelautert
pushed a commit
that referenced
this issue
Sep 21, 2023
filipelautert
pushed a commit
that referenced
this issue
Sep 21, 2023
rberezen
pushed a commit
that referenced
this issue
Sep 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search first
Description
Some RDBMS support units like CHAR in the length specifier, so schemas do exists using CHARACTER(n CHAR) or VARCHAR(n CHAR) units.
Unfortunately this leads to an SQL exception when applying such a schema on PostgreSQL, as that RDBMS does not support the CHAR specifier.
Steps To Reproduce
Expected/Desired Behavior
PostgreSQL ignores the
CHAR
unit, as it implicitly interprets the value as characters.Liquibase Version
master
Database Vendor & Version
PostgreSQL 15.3
Liquibase Integration
N/A
Liquibase Extensions
N/A
OS and/or Infrastructure Type/Provider
Debian 12.2.0-14
Additional Context
N/A
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: