Downgrading then upgrading redash schemas doesn't work about redash HOT 6 OPEN

Yeah, it's a bit unfortunate -- I assume the alembic db migrations were automatically generated, and were just wrong in this case. I think we need to verify (via pg_dump or similar) that the schema is as you'd expect after an arbitrary number of upgrades and downgrades.

FWIW my testing setup is to do this to downgrade:

./manage.py db downgrade fd4fc850d7ea

And this to upgrade:

./manage.py db upgrade

from redash.

Found an additional gotcha (schedule for queries can get set to the string "null" on downgrade), updated description.

from redash.

@wlach thanks for a finding
could you please submit PR with a fix?

from redash.

@wlach thanks for a finding could you please submit PR with a fix?

Will see what I can do.

from redash.

Oh, this all doesn't sound good.

Breaking the schema when downgrading is something we'd better fix.

The rough plan is to enable automatic schema upgrades when Redash starts (rather than a manual process). So being able to downgrade stuff when needed for some reason is probably pretty important.

from redash.

@wlach thanks for a finding could you please submit PR with a fix?

Will see what I can do.

Update: I haven't had time to look at this and am not sure when I will.

from redash.