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

Suggestion: SQLite backend #87

Open
sammcj opened this issue Jan 30, 2019 · 2 comments
Open

Suggestion: SQLite backend #87

sammcj opened this issue Jan 30, 2019 · 2 comments

Comments

@sammcj
Copy link

sammcj commented Jan 30, 2019

Looking at this neat little project I was a bit surprised that it needed a full (OR)DBMS.

I love PostgreSQL, but sometimes for small, self-contained projects I think that SQLite is (perhaps) a wise choice - especially when it's going to often be run in Docker containers for local use as it saves having to pull down a full PostgreSQL Docker image and run a container for it.

If it's not worth the effort feel free to reject the suggestion :)

@davidfetter
Copy link

With utmost respect, this isn't the era when a few megabytes' worth of infrastructure is even noticeable. Is it really all that burdensome to be running PostgreSQL?

@sammcj
Copy link
Author

sammcj commented Mar 8, 2020

I understand what you’re saying, but I don’t think that to run a simple app you should have to install, configure and maintain a full database server.

It’s not about the cost of running it - it’s about the practicality. For example if you want to run this ad-how on your laptop when you need it - it’s a pain to have to install and run a database server.

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

No branches or pull requests

2 participants