2 ms·
The first time you have to add a new schema value, you'll realise you needed "unknown" or similar - because during an upgrade your old systems need a way to dea
by XorNot 2y ago
The first time you have to add a new schema value, you'll realise you needed "unknown" or similar - because during an upgrade your old systems need a way to deal with new values (or during a rollback you need to handle new entries in the database).
- sitkack 2y agoYour comment is the only in the entire discussion that mentions "schema". Having an "other" in a schema is a way to ensure you can run n and n+1 versions at the same time. It is Data Model design, of which API design a subset. You can only ever avoid having an other if 1) your schema is fixed and 2) if it is total over the universe of values.