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

Support SQLite #32

Open
n1trux opened this issue Jan 4, 2020 · 4 comments
Open

Support SQLite #32

n1trux opened this issue Jan 4, 2020 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@n1trux
Copy link
Contributor

n1trux commented Jan 4, 2020

I'd really like to run this on devices without a "fat" DB daemon, which is where SQLite would be beneficial.

@wernersbacher
Copy link

wernersbacher commented Jan 9, 2020

+1, it would make it really quick and easy. SQLite can handle websites with up to millions of request a day. So for a self hosted private service, SQLite should be strong enough.

@jrie
Copy link
Owner

jrie commented Jan 14, 2020

I agree, it might be nice to have SQLite support - but at the moment, there are several database changes going on and possible coming and adding another database to work with, might be slowing down the development.

When things are more settled this is definitely something to look into.

@jrie jrie added the enhancement New feature or request label Jan 14, 2020
@jrie jrie added the help wanted Extra attention is needed label Mar 31, 2020
@n1trux
Copy link
Contributor Author

n1trux commented Oct 4, 2020

at the moment, there are several database changes going on and possible coming and adding another database to work with, might be slowing down the development.

Or you could use an abstraction layer which works with both.

I found Medoo on the lightweight-php list which "supports all SQL databases, including MySQL, MSSQL, SQLite, MariaDB, PostgreSQL, Sybase, Oracle and more".

Changes to the database scheme could be implemented by properly versioning the database (related: #34) and creating migrations. These could easily be written with Medoo if there's a mismatch between installed DB version and upgraded DB version.

@schnoog
Copy link
Contributor

schnoog commented Oct 24, 2020

Would prefer to wait for SergeyTsalkov/meekrodb#66 to keep the current wrapper syntax alive.

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

No branches or pull requests

4 participants