eContract DB Diagram

PK primary key FK foreign key { } JSON column foreign-key relation reference inside JSON (not enforced) Hover a table to highlight its relations.

Relationships

contracts 1 — N contract_sections via contract_id. Each contract has one main section and any number of sub sections.
contract_sections 1 — N user_contracts via contract_section_id, which always points to the main section.
users 1 — N user_contracts via user_id (the contractor).
user_contracts.sub_contract[].source_section_id points to the selected sub sections. It lives inside JSON, so the database doesn't enforce it.
user_contracts 1 — 1 contract_details via user_contract_id. Every template input key becomes a column there. Inputs from sub-sections are NULL when that sub-section isn't selected.