Then build with SQLITE_DEFAULT_FOREIGN_KEYS=1 to make it opt-out (and to opt-out... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

ncruces 22 days ago | parent | context | favorite | on: Limbo: A complete rewrite of SQLite in Rust

Then build with SQLITE_DEFAULT_FOREIGN_KEYS=1 to make it opt-out (and to opt-out you'd need to inject SQL).

As for STRICT: if you make your tables STRICT, there's no opt-out.

So why is this an issue? Do you want them to break the file format to say "from this version forward, all tables are STRICT"? What does that really buy you?

It's an embed database: anyone who can mess with your database and circumvert integrity can also open the file and corrupt it.

IshKebab 21 days ago [–]

> What does that really buy you

It removes a footgun for new users. That's not an insignificant benefit.

Probably not worth the backwards compatibility cost, but it definitely is an issue.

ncruces 21 days ago | [–]

My builds of SQLite do enable foreign keys by default.

This is easy to do for any project using the amalgamation.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact