Skip to content
This repository was archived by the owner on Sep 21, 2024. It is now read-only.

[5] Refactor backend to use PostgreSQL #110

Open
MitchellDill opened this issue Aug 13, 2019 · 0 comments
Open

[5] Refactor backend to use PostgreSQL #110

MitchellDill opened this issue Aug 13, 2019 · 0 comments
Labels
back end Bugs/Implementation on server/DB stretch goal Features beyond MVP functionality - not to be addressed until MVP in place

Comments

@MitchellDill
Copy link
Contributor

If we want to have a more cogent backend design, we should create multiple tables for our data (users, transactions, accounts, etc), and create endpoints to accompany those, as opposed our current (expedient) MVP-focused database design.
@MitchellDill MitchellDill added back end Bugs/Implementation on server/DB stretch goal Features beyond MVP functionality - not to be addressed until MVP in place labels Aug 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
back end Bugs/Implementation on server/DB stretch goal Features beyond MVP functionality - not to be addressed until MVP in place
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MitchellDill