Octo should refuse to startup if database format is higher than build format
Final Release Note
Description
@shabiel came across an issue when looking into #211 (closed) (!1244 (merged)).
The usecase is as follows:
- A VIEW was created in #211 (closed) branch (which has a higher value of FMT_BINARY_DEFINITION than the master branch)
- Branch was switched to master
- Octo was started
- An error saying
CREATE VIEW
cannot be parsed was seen.
This happened as a binary upgrade happened at the start of Octo. The above case is specific to VIEWS but this is a general issue where any new feature usage which stores binary information can result in.
In cases like these where the binary format changed from a higher value to a lower value an upgrade should be avoided and an error should be generating saying the DB has binary data which is not compatible with the current binary format definition.