НС
Size: a a a
НС
MI
MI
MI
AM
Ei
AM
Ei
AM
Ei
AM
Sven Wegener
Jul 3 9:45 AM
↩
Patch Set 6: Workflow-1
I'm putting this on hold, doing the enum migrations like this does not change to enum definition on PostgreSQL.
Jens Harbott (frickler)
Jul 3 11:51 AM
↩
Patch Set 6:
It looks to me like the initial error is fixed by this patch and we just have collected some other issue(s) during the time that the postgres job was broken. So I'd be fine with merging this as a first step and then fixing the other things iteratively.
I've proposed to make the postgres job to be non-voting for the time being in order to allow that.
Jens Harbott (frickler)
Jul 3 11:52 AM
↩
Patch Set 7: Patch Set 6 was rebased
Sven Wegener
Jul 3 12:23 PM
↩
Patch Set 7:
I agree, looking at the CI output the errors come from different parts of the code.
This commit fixes both errors I mentioned in the commit message, but looking at the final database schema, after running the migrations, the actual enum changes are not being applied on PostgreSQL at all.
We need a completely different way for enum migrations on PostgreSQL.
Do we want to do that in an additional migration file, merging this commit before that, or fix the migrations in place, as they currently cannot be applied at all on PostgreSQL?
AM
Ei
AM
y
AM
MI
MI
MI
PK