Support multiple databases & schemas?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- databases, full-stack
Research direction
No files, tests, or entry points are named. Start by deciding how database and schema context should be configured and represented in frontend and API URLs, then define the switcher behavior. Done means one UI instance can serve configured databases or schemas with unambiguous, shareable context URLs.
Written by the indexing model from the issue text.
Description
A user asked for our UI to be capable of letting a single UI instance serve multiple databases so they don't require a single UI deployment per database. I've run into the frustration of having to have many different UI deployments at my day job, so I agree this would be nice.
We might also be able to tackle multiple schemas using the same mechanism here. Imagine if the UI is able to somehow take a config of DB names to URLs. There could be a switcher in the menu bar to allow you to change the "context" of which one you're working on.
The big question I have is how this would be reflected in URLs for either the frontend or the API backend. Does the DB name become a required part of the path or a query param in either case? On the frontend, you could keep it as a local storage setting (like switching from light to dark mode) and keep it out of the URL, but this would have some downsides (URLs not as easily shareable between users). Instead of that, we may want to structure our URLs to include the DB name as a prefix.
cc @brandur
- Dominant language
- TypeScript
- Stars
- 236
- Forks
- 39
- Avg merge
- 3h 40m
- Merged PRs (30d)
- 23
Contributor guide
No contributing guide indexed for this repository
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.
More from riverqueue/riverui
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
riverqueue/riverui#448 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
riverqueue/riverui#102 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
riverqueue/riverui#590 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
riverqueue/riverui#479 · 3 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
riverqueue/riverui#441 · 6 comments ·
All issues in riverqueue/riverui
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·