-
Notifications
You must be signed in to change notification settings - Fork 115
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
createTable/column is not behaving the same as addColumn #71
Comments
@bassmartin Can you provide a sample project? |
@Schlogen see https://github.com/bassmartin/sample_grails_dbm |
Essentially the issue is here: https://github.com/liquibase/liquibase/blob/91a4e47bfe278e2ac17d1a8cca932554547fc5e7/liquibase-core/src/main/java/liquibase/datatype/core/DateTimeType.java#L144 The database is |
The root of this is how columns are handled when a column is missing vs when a table is missing: How columns are handled when a table is missing: https://github.com/liquibase/liquibase/blob/0c2c0fea18abeda20ab9b9921b11bb3dfaad7d71/liquibase-core/src/main/java/liquibase/diff/output/changelog/core/MissingTableChangeGenerator.java#L70 How columns are handled when a column is missing: |
The MissingColumnChangeGenerator should use the same logic as MissingTableChangeGenerator |
@nvoxland Is there an issue for this in your system anywhere? |
When there a table creation written by the plugin
createTable/column
:java.lang.Integer = type: "INT"
org.joda.time.LocalDateTime = type: "timestamp" (my dialect is not taken into account, it should be timestamptz)
When there is a column added written by the plugin
addColumn
:java.lang.Integer = type: "int4"
org.joda.time.LocalDateTime = type: "timestamptz"
The schema is not consistent.
The text was updated successfully, but these errors were encountered: