4 ms·
I don't see why this must be a breaking change. (1) Add a flag when opening a database to show that you want data types enforced. (2) Add code to all the inpu
by nine_k 7y ago
I don't see why this must be a breaking change.
(1) Add a flag when opening a database to show that you want data types enforced.
(2) Add code to all the input pathways to check for type compliance. This way a database with correct data types will stay correct.
(3) Do not change anything in the storage layer.
What am I missing?
- murftown 7y agoSeems like (1) is doable, as long as it's opt-in. But if it becomes the default behavior, existing applications would break when they do something against the type system. I'm not sure what (2) buys you.
- nine_k 7y ago(1) is the interface to trigger (2).
- scottlamb 7y agoThis is very similar to what they did for foreign key support. https://www.sqlite.org/pragma.html#pragma_foreign_keys https://www.sqlite.org/pragma.html#pragma_foreign_keys