Dolt does foreign key checks on update when no foreign key columns have changed
Open
performance
sql
- Dominant language
- Go
- Stars
- 24.4k
- Forks
- 873
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 120
Description
Foreign key checks are expensive, and we currently check them on every row that gets changed in an `UPDATE`, even if no columns with a foreign key constraint have changed. We should fix that.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the UPDATE path and its foreign-key validation checks; the issue does not name a file, test, or entry point. Done means UPDATE skips foreign-key checks when no constrained columns changed, while still checking them when relevant columns are modified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100