Flask-Lastuser model changes

[Kiran Jonnalagadda]

Hello all,

I'm considering adding more columns to the User model in Flask-Lastuser. Lastuser recently acquired a `status` column that allows a user account to be suspended or marked as merged. There is no such column in the Flask-Lastuser, so no way to suspend a user at the app level.

Adding a column will affect all apps that use Flask-Lastuser, which will mean they need migrations. I'm not aware of any means by which Flask-Lastuser can itself publish an Alembic migration path for client apps.

I'm guessing this means migrations will be mandatory for ALL apps henceforth. Anyone have issues with that?

Kiran

-- 

Kiran Jonnalagadda

+91-99452-35123

http://hasgeek.com