🔗 SQLite should have (Rust-style) editions

SQLite is known for its simplicity but it faces significant issues due to its poor default settings. For instance, foreign key constraints are ignored by default, which compromises data integrity. This flaw allows an invalid reference to reappear, posing severe risks of data corruption. Additionally, SQLite's loose data type handling means that incorrect types can be inserted, complicating data validation. The absence of a global pragma for strict tables also leaves it up to developers to remember to apply stricter typing, further increasing the chance of errors.

Another glaring issue is the SQLITE_BUSY error that can occur when multiple processes try writing simultaneously, which can lead to unexpected software crashes. Performance defaults are also subpar, as SQLite's Write-Ahead Log (WAL) is disabled by default, despite its benefits in enhancing write speeds. The article proposes that SQLite should adopt editions similar to Rust's versioning to tackle these persistent problems and make its defaults safer and more efficient.