create Locker schema on backend to define how frontend renders and updates Locker information

Question

create Locker schema on backend to define how frontend renders and updates Locker information

Opened this issue 3 years ago · 1 comments

In order to limit locker status options, use locker_status table to manage available values for locker_status.

Answer 1 · 2022-01-24T15:34:43.000Z

As referenced in issue #3, the most robust and thorough solution to the Locker schema would be to create several parent tables that define the different options, eg. locker_status table that associates each status with an ID number, and have the locker table be the child table that references each parent table using an ID. The other option is just to create a separate table, say locker_schema, whose rows contain the possible, allowable values for the columns in the locker table.

The first option is a much more robust and thorough approach but definitely requires much more work.