-
Notifications
You must be signed in to change notification settings - Fork 34
Detect usage of the strings for numeric/boolean types in Liquibase migrations #1111
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
Comments
Another case that hasn't been spotted in #1107: <column name="series_id" value="1" />
<column name="number_of_stamps" value="1" /> |
It seems like we can use |
Another idea is to detect usage of old schema: http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.0.xsd instead of 3.1 |
Yet another one: each |
One more gotcha -- MySQL doesn't support Update: use |
We can also force a foreign keys to have a name. Also we can check that date fields have names with suffix "_at" and fields that references users have suffix "_by". |
|
|
It has turned out that |
Liquibase 4.5.0 has introduced quality checks and at least it has a rule to ensure that every changeset has a context attribute: https://docs.liquibase.com/concepts/advanced/configuring-quality-checks.html#Ensure2 |
It has turned out that |
|
We should use
valueBoolean
in this case --https://www.liquibase.org/documentation/column.htmlThe text was updated successfully, but these errors were encountered: