Skip to content
This repository has been archived by the owner on Apr 20, 2023. It is now read-only.

Migrate away from storing tables in the front end. #80

Open
f-gate opened this issue Feb 8, 2023 · 0 comments
Open

Migrate away from storing tables in the front end. #80

f-gate opened this issue Feb 8, 2023 · 0 comments

Comments

@f-gate
Copy link
Member

f-gate commented Feb 8, 2023

Instead of holding for example suggestedIndustries[] in the front end and in the db, one should call the db so that everything stays consistent and we don't violate foreign keys/ have to update the code twice for a single update.

This means creating models for each of the tables and providing basic selects.

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

No branches or pull requests

1 participant