Correction: we're likely to encounter this problem in 5.0.1 as well, a non-zero DB schema version number is required to reproduce.
Correction: we're likely to encounter this problem in 5.0.1 as well, a non-zero DB schema version number is required to reproduce.