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.

Sign up for GitHub

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

Jump to bottom

Data persistence #14

Open
kms70847 opened this issue Jul 25, 2016 · 4 comments
Open

Data persistence #14

kms70847 opened this issue Jul 25, 2016 · 4 comments
Assignees
@kms70847
Labels
enhancement

Comments

@kms70847
Copy link
Contributor

We need a DB and an interface for talking to it. Without this, several other issues can't be resolved.
@kms70847 kms70847 self-assigned this Jul 25, 2016
@kms70847
Copy link
Contributor Author

Briefly discussed this issue in chat. Fizzy, Poke, and Jon suggest Postgres. ( http://chat.stackoverflow.com/transcript/message/31915475#31915475 http://chat.stackoverflow.com/transcript/message/31915478#31915478 http://chat.stackoverflow.com/transcript/message/31915544#31915544 )

@kms70847
Copy link
Contributor Author

Jon also suggests using an ORM such as SQLAlchemy so it's easy to switch between backends. ( http://chat.stackoverflow.com/transcript/message/31915544#31915544 ).

@kms70847
Copy link
Contributor Author

All of this sounds good to me. sqlite3/postgres as appropriate, using SQLA for a consistent interface.

@davidism
Copy link
Member

I was imagining I'd just use sopython, although I'd be ok with standing up another Flask app as a separate api too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kms70847 kms70847

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@davidism @kms70847