WIP: Keep multiple database instances stored in static array #36

Draft
vlw wants to merge 1 commit from feat/multiple-database-instances into master
vlw commented 2026-05-20 17:07:52 +02:00 (Migrated from codeberg.org)

This is not a solution to issue #31. It's another hack that will allow connections to multiple databases to say open. A database specific database instance can be recalled by passing an optional string Database::instance("db_name") which will [create if it does not exist, and] return a Database instance for that database name.

This is not a solution to issue #31. It's another hack that will allow connections to multiple databases to say open. A database specific database instance can be recalled by passing an optional string `Database::instance("db_name")` which will [create if it does not exist, and] return a `Database` instance for that database name.
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/multiple-database-instances:feat/multiple-database-instances
git switch feat/multiple-database-instances

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff feat/multiple-database-instances
git switch feat/multiple-database-instances
git rebase master
git switch master
git merge --ff-only feat/multiple-database-instances
git switch feat/multiple-database-instances
git rebase master
git switch master
git merge --no-ff feat/multiple-database-instances
git switch master
git merge --squash feat/multiple-database-instances
git switch master
git merge --ff-only feat/multiple-database-instances
git switch master
git merge feat/multiple-database-instances
git push origin master
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
vlw/scaffold!36
No description provided.