Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mysql/MariaDB #1816

Closed
Abraka opened this issue Jun 9, 2023 · 3 comments · Fixed by #2300
Closed

Mysql/MariaDB #1816

Abraka opened this issue Jun 9, 2023 · 3 comments · Fixed by #2300
Labels
enhancement New feature or request

Comments

@Abraka
Copy link

Abraka commented Jun 9, 2023

Is your feature request related to a problem?

Base on reading memos/blog storage text(storage comparison) it looks like there is not a "storage" solution for effective local hosting if you have bigger installation or lets say installation which will have 1-2 years of memos.

Describe the solution you'd like

Add ability to specify external Mysql/MariaDB for memos to be abble to use them as storage.

Additional context

No need to create some crazy docker combos crazyness like separate DB installation in docket etc. Just add feature to define mysql connection to external source. Thats all. Thx.

@Abraka Abraka added the enhancement New feature or request label Jun 9, 2023
@athurg
Copy link
Contributor

athurg commented Jun 13, 2023

This will be cool for support more than one database backend.

But it'll also cause many problems about concurrent and other resource shared.

@waynexia
Copy link
Contributor

I am also looking forward to this feature!

But it'll also cause many problems about concurrent and other resource shared.

Comparing to sqlite we are currently using, MySQL / PG / MariaDB seem to meet the same requirement. Which specific problem are you referring to?

@siddharthalodha
Copy link

+1 for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants