We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have the following column definition from an historical changeset. Don't ask me why there is a precision ...
<column name="COLUMNNAME" type="BOOLEAN(1)"> <constraints nullable="false"/> </column>
Which gives me the following Error with liquibase 4.21.1
Syntax error in SQL statement "CREATE TABLE TABELNAME (COLUMNNAME BOOLEAN[*](1) NOT NULL)"; expected "ARRAY, INVISIBLE, VISIBLE, NOT NULL, NULL, AS, DEFAULT, GENERATED, ON UPDATE, NOT NULL, NULL, AUTO_INCREMENT, DEFAULT ON NULL, NULL_TO_DEFAULT, SEQUENCE, SELECTIVITY, COMMENT, CONSTRAINT, COMMENT, PRIMARY KEY, UNIQUE, NOT NULL, NULL, CHECK, REFERENCES, AUTO_INCREMENT, ,, )"
Because formally I struggled with this Bug #3300 and an older Liquibase version I think there has to be a similar handling for the boolean datatype.
Define a column like this in a changeset
Column with BOOLEAN(x) is correctly translated.
4.21.1
H2 2.1.214
CLI, maven
No response
MacOS Ventura 13.3.1
The text was updated successfully, but these errors were encountered:
liquibase#4227 fix for BOOLEAN with precision like BOOLEAN(1)
f234a89
Removed needs_guidance label, since @sfrevel already provides a PR for this issue. Thank you for that, @sfrevel!
needs_guidance
Sorry, something went wrong.
Merge pull request #4228 from sfrevel/feature/4227
da5182d
#4227 fix for BOOLEAN with precision like BOOLEAN(1)
Successfully merging a pull request may close this issue.
Search first
Description
I have the following column definition from an historical changeset. Don't ask me why there is a precision ...
Which gives me the following Error with liquibase 4.21.1
Because formally I struggled with this Bug #3300 and an older Liquibase version I think there has to be a similar handling for the boolean datatype.
Steps To Reproduce
Define a column like this in a changeset
Expected/Desired Behavior
Column with BOOLEAN(x) is correctly translated.
Liquibase Version
4.21.1
Database Vendor & Version
H2 2.1.214
Liquibase Integration
CLI, maven
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
MacOS Ventura 13.3.1
Additional Context
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: