GitHub user zyratlo added a comment to the discussion: Notebook Migration tool: database schema design
## Proposed New Design <img width="1160" height="623" alt="Screenshot 2026-02-10 042826" src="https://github.com/user-attachments/assets/1efef9e7-3114-4cdc-9b8c-4dadae97619c"; /> ### Changes from the current design - A `workflow` table can now relate to zero or many `notebook` tables - A new attribute `nid` in the `notebook` table acts as another primary key - `workflow_mapping_notebook` now references the `nid` attribute as a foreign key, and uses it as a primary key - A single `notebook` table can relate to one or many `workflow_mapping_notebook` tables, while a single `workflow_mapping_notebook` table must relate to one and only one `notebook` table ### Explanation This new design allows for any number of notebooks to relate to a single workflow, which was a limitation of the current design. Now, the design allows for any number of notebook revisions alongside workflow revisions with the new `nid` attribute. Whenever the notebook is changed, a new `nid` is generated, allowing the `workflow_notebook_mapping` table to adequately save a new mapping even when the `vid` remains the same. GitHub link: https://github.com/apache/texera/discussions/4175#discussioncomment-15756268 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
