This corrects #396 in which we were a bit too quick actually dropping
the column. As per our migration policy, we should first update the code
to work without the column, then drop the column at least one release
later.