fix(db:migrate): fix migration user 'confirmed' column migration

This change fixes the migration on the `user` table, `confirmed` column to be compatible with PostgreSQL and MySQL databases.

Fixes #635 which introduced a breaking change for MySQL databases and resolves #1446.

```
Tested on:
- PostgreSQL:14 - WORKING
- PostgreSQL:15 - WORKING
- MariaDB:10.11 - WORKING
- MariaDB:10.10 - WORKING
- MariaDB:10.9  - WORKING
- MariaDB:10.8  - WORKING
- MariaDB:10.7  - WORKING
- MariaDB:10.6  - WORKING
- MariaDB:10.5  - WORKING
- MariaDB:10.3  - WORKING
```
This commit is contained in:
Nigel Kukard 2023-03-14 12:53:30 +00:00
parent 4420621cfe
commit 61e607fb3f

View File

@ -23,7 +23,7 @@ def upgrade():
with op.batch_alter_table('user') as batch_op: with op.batch_alter_table('user') as batch_op:
user = sa.sql.table('user', sa.sql.column('confirmed')) user = sa.sql.table('user', sa.sql.column('confirmed'))
batch_op.execute(user.update().values(confirmed=False)) batch_op.execute(user.update().values(confirmed=False))
batch_op.alter_column('confirmed', nullable=False) batch_op.alter_column('confirmed', nullable=False, existing_type=sa.Boolean(), existing_nullable=True, existing_server_default=False)
def downgrade(): def downgrade():