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 to using our own Schemas #5

Open
PeterDKC opened this issue Oct 3, 2022 · 0 comments
Open

Switch to using our own Schemas #5

PeterDKC opened this issue Oct 3, 2022 · 0 comments
Assignees

Comments

@PeterDKC
Copy link
Collaborator

PeterDKC commented Oct 3, 2022

We're going to use our own DB schemas for Models instead of LegiScan schemas. In order to effect this, there's a few steps

[ ] Delete all the current Models
[ ] Create migrations for all of the Models (probably do one by one here)
[ ] New Model files to leverage those schemas
[ ] Create new Import steps to take the data from the LegiScan import and pipe it into the new tables using firstOrCreate()
[ ] Tests and such

Feature Branch: feature/5-switch-to-our-schema

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

No branches or pull requests

1 participant