tursodatabase / tursodatabase/libsql
SQLite allows foreign keys on non-existing columns?
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
There's a report of SQLite allowing the creation of a foreign key on a non-existing column. Let's look into this to understand if that's really something SQLite is supposed to allow and then think about potential ways to prevent that in libSQL.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reproducing the reported foreign-key definition in SQLite and libSQL, then compare the behavior with the expected validation rules. Done means establishing whether this is SQLite-compatible and documenting an agreed approach for preventing it in libSQL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100