Skip to content

Schema does not match #2028

Answered by simolus3
fernandaalmeida asked this question in Q&A
Discussion options

You must be logged in to vote

Looking at the schema json, it seems like the DEFAULT 1 is indeed unexpected.

A column with a definition of NOT NULL DEFAULT 1 is different from a NOT NULL-only column, so drift complains about the found difference. Everything seems to be working as intended here? If you want the default to be there, you also need to define the column with that default in the original table used by the main database.

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by fernandaalmeida
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants