You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not quite sure that is my mistake or its a bug of peewee_migrate.
left is my first migration, and i didn't change followed table, but edited another table. Then I generated a migration.
But i found that pw.CharField and pw.InteferField are both consider changed. Seems that all field with default value are considered changed and automatically get a migration.
The text was updated successfully, but these errors were encountered:
I'm not quite sure that is my mistake or its a bug of peewee_migrate.
left is my first migration, and i didn't change followed table, but edited another table. Then I generated a migration.
But i found that pw.CharField and pw.InteferField are both consider changed. Seems that all field with default value are considered changed and automatically get a migration.
I encounter the same problem。It is a bug,the default value show not generate "constraints" param,but generate "default" param
I'm not quite sure that is my mistake or its a bug of
peewee_migrate
.left is my first migration, and i didn't change
followed
table, but edited another table. Then I generated a migration.But i found that
pw.CharField
andpw.InteferField
are both consider changed. Seems that all field with default value are considered changed and automatically get a migration.The text was updated successfully, but these errors were encountered: