You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'll need new endpoints to update the status for use with the status/timeline component (#84)
Currently we've got a status field in the participants table, it's an enumerable.
We need to add another field to this table to store which databases has been checked for this individual.
For init.sql database, I was thinking to create a new table for status and background check and define in the following way. Please let me know if you have any suggestions.
CREATE TABLE status(
id SERIAL PRIMARY KEY,
status ENUM(
'New Case',
'Obligation Form Completed',
'Waiting for Background Check',
'Attorney Review',
'Sent to Court',
'Received From Court',
'Sent to Participant',
'Close')
)
CREATE TABLE background_check(
id SERIAL PRIMARY KEY,
cchrs BOOLEAN,
w&w BOOLEAN,
dmv BOOLEAN,
tcis BOOLEAN,
FOREIGN KEY (participant_id) REFERENCES participants (id)
)
tienyuan
changed the title
Add backend and endpoints related to the status/timeline component
Rewrite this issue: Add backend and endpoints related to the status/timeline component
Jul 2, 2019
We'll need new endpoints to update the status for use with the status/timeline component (#84)
Currently we've got a status field in the participants table, it's an enumerable.
We need to add another field to this table to store which databases has been checked for this individual.
According to http://www.postgresqltutorial.com/postgresql-json/ we can use the json datatype to store json. And the json we store can be something like ...
We want to be able to change each database value to true/false independently.
Notes:
The text was updated successfully, but these errors were encountered: