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

Switch backend to PostgreSQL #1

Open
pganssle opened this issue Jan 16, 2017 · 0 comments
Open

Switch backend to PostgreSQL #1

pganssle opened this issue Jan 16, 2017 · 0 comments
Milestone

Comments

@pganssle
Copy link
Owner

Currently I'm using some sort of cobbled-together database of YAML files. I was hoping that this would be performant enough for the short term to not make much difference, but with only around 450 books there's significant lag in initial startup, and it causes some issues.

The main advantage to using YAML files was that it would be easy to edit them by hand before I had a proper interface for manual tweaks to metadata, but I think the better approach to this is the one I took with find_missing_books, where I dump a subset of the database as YAML, then update the full database from there. I think something like that should be an easier stop-gap before I get a proper editing system.

@pganssle pganssle added this to the 0.2.0 milestone Jan 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant