No, I don't believe a cascade will occur, which means all old sql statements would lose their arguments. However, I think this may be unavoidable, as there is no way to remove the unique constraint from the value column without knowing the name of the constriant, which, unless you added the constraint using Alembic rather than using the models in sqlalchemy, we don't have (this will probably cause other issues in the future as well :cry:).

This sucks, but I'm not sure there's any way around it if we want to get arguments working with postgres dbs.

What I will do is put a couple more checks in for empty arguments, so we don't break the UI for older sql statements that are missing their args.