Sync panics on sqlite named foreign key
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9.9k
- Forks
- 734
- Avg merge
- 6h 36m
- Merged PRs (30d)
- 8
Description
2.0.0-rc.41 (.42 is not usable for me, forget why)
If a foreign key has a name (not anonymous) sync panics, providing no context (e.g. which table, which key).
If I manually set a FK to have a name sync fails. Remove the name and it seems ok.
Default behaviour for FK generation in tools is to make a name. I think this is expected behaviour.
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
Start by reproducing SQLite sync with a named foreign key and compare it with an anonymous key. Trace the panic from the sync entry point to identify where table and key context is lost; done means named foreign keys sync without panicking and failures identify the table and key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100