-
-
Notifications
You must be signed in to change notification settings - Fork 956
default column values are incorrectly handled by diffs #14477
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
Did you specify |
Yes, I did. |
FYI, I have just added the following to a domain:
And liquibase correctly detects the default, and does no longer generate a
|
@edwardotis |
It doesn't work with It works with with strings, numbers, and |
It seems like |
Given
a. I have to hand correct the diff to add defaultvalueboolean:
changeSet(author: "me (generated)", id: "1486375845934-1") { addColumn(tableName: "apple") { column(name: "is_good", type: "boolean", defaultValueBoolean: false) { constraints(nullable: "false") } } }
b. After applying update, the next diff will try to remove it
So basically, the plugin (or underlying libraries) break default values.
http://docs.grails.org/3.1.14/ref/Database%20Mapping/column.html
runtime 'org.grails.plugins:database-migration:2.0.0
grails 3.1.14
postgres 9.6
java 8
The text was updated successfully, but these errors were encountered: