oxidecomputer / oxidecomputer/omicron
Tracking Issue for Database Improvements
Open
Nobody has claimed this yet.
database
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Tracking issue for improvements interacting with the database. Please edit and add issues accordingly.
Async
Pools
Transactions & CTEs
- https://github.com/oxidecomputer/omicron/issues/3814
- https://github.com/oxidecomputer/omicron/issues/3304
- https://github.com/oxidecomputer/omicron/issues/4190
- https://github.com/oxidecomputer/omicron/issues/973
Updates
- https://github.com/oxidecomputer/omicron/issues/210
- (Related to #210) Audit usage of
SELECT *andRETURNING *, prefer explicit columns so we access columns consistently across updates
Safety
- https://github.com/oxidecomputer/omicron/issues/4144
- https://github.com/oxidecomputer/omicron/issues/1168
- https://github.com/oxidecomputer/omicron/issues/263
Ergonomics
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
Review the linked issues under Async, Pools, Transactions & CTEs, Updates, Safety, and Ergonomics to understand the individual database improvements. Update this checklist only when the referenced work or newly identified issues have clear status; done means the tracking list accurately reflects the outstanding database work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100