Feat/add db tables #3
Conversation
|
@tmastrom what is the status of this card? |
|
@MichaelVeniez it will be an ongoing process. We haven't established a solid ERD yet as we're still waiting for information on a certain data set... It has some things that will stay, and some things that will go. Dylan and I decided to keep the PR alive so that we can just strip out tables we don't need rather than start a new PR and rewrite everything that's going to stay. The card itself likely won't be "finishable" until we have more information. The schema won't hit its final for a while, but once we have the basic tables we know we need in, we can call it done. |
|
The above comment holds true, but I am putting it to the development team. If you'd prefer to continue the existing branch and clean out what isn't needed, add what is, you are free to. If you'd prefer to create new branches and smaller tickets, that is also viable. Make sure to grab the necessary functions and policies (something the developers should sync about) out of the existing PR. |
Pull #2 has to be merged before this, then this will need a rebase.
Pull to begin adding tables to the DB.