Known data model changes
Made some changes to the data model, making things a little bit more flexible going forward. BACK UP BEFORE UPGRADING!
A heads up to those who are following Known GitHub HEAD!
I’ve just merged a change to Known core that makes a significant change to Known’s *sql core (mysql and Postgres). This change splits the metadata table into one metadata table per collection.
This simplifies the data model, which makes certain stuff easier going forward (import/export, GraphQL APIs etc). It also means we can leverage the DBMS in order to maintain data integrity.
This is a significant change, so it goes without saying that you need to BACK UP YOUR DATABASE BEFORE UPGRADING!
Can this be used if we are using the 1.1.7 build from your own unofficial releases?
Known should detect the schema change and roll you up. Make sure you back up before hand though, because database schemas are complex things to manage.