starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #130] [Feature]: MySQL/PostgreSQL database #72

New issue

Closed

opened 2026-05-07 00:05:52 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

2026-05-07 00:05:52 +02:00

Owner

Originally created by @elit3ge on GitHub (Jan 22, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/130

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

It would be great to take this out of the SQLite database and use my existing infrastructure.

Proposed Solution

Implement external database management.

Alternatives Considered

No response

Feature Category

Other

Priority

Nice to have

Mockups or Examples

No response

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @elit3ge on GitHub (Jan 22, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/130 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case It would be great to take this out of the SQLite database and use my existing infrastructure. ### Proposed Solution Implement external database management. ### Alternatives Considered _No response_ ### Feature Category Other ### Priority Nice to have ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware

2026-05-07 00:05:52 +02:00

closed this issue
added the
wontfix
label

BreizhHardware commented

2026-05-07 00:05:53 +02:00

Author

Owner

@maziggy commented on GitHub (Jan 22, 2026):

Certainly a nice feature for the future. Need to tag that as future feature, because currently there is no time for it.

@maziggy commented on GitHub (Jan 22, 2026): Certainly a nice feature for the future. Need to tag that as future feature, because currently there is no time for it.

BreizhHardware commented

2026-05-07 00:05:53 +02:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 16, 2026):

This issue has been marked as stale due to inactivity. It will be closed in 7 days if there is no further activity.

@github-actions[bot] commented on GitHub (Feb 16, 2026): This issue has been marked as stale due to inactivity. It will be closed in 7 days if there is no further activity.

BreizhHardware commented

2026-05-07 00:05:53 +02:00

Author

Owner

@maziggy commented on GitHub (Mar 7, 2026):

We decided to not go this way. Using another database than Sqlite has no real advantages and would increase the required work to maintain the code.

@maziggy commented on GitHub (Mar 7, 2026): We decided to not go this way. Using another database than Sqlite has no real advantages and would increase the required work to maintain the code.

BreizhHardware commented

2026-05-07 00:05:54 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 5, 2026):

We decided to move forward with Postgresql instead of Mysql. Available in branch dev or daily builds.

@maziggy commented on GitHub (Apr 5, 2026): We decided to move forward with Postgresql instead of Mysql. Available in branch dev or daily builds.

BreizhHardware referenced this issue

2026-05-07 00:15:00 +02:00

[PR #81] [MERGED] v0.1.6b7 #928

BreizhHardware referenced this issue

2026-05-07 00:15:17 +02:00

[PR #241] [MERGED] Fix for Information exposure through an exception #72 #976

BreizhHardware referenced this issue

2026-05-07 00:15:17 +02:00

[PR #242] [MERGED] Fix for Information exposure through an exception #72 #978