Multiple Records Associated with a Single Record #667
Replies: 5 comments 5 replies
-
@ghislaineguerin I like the concept here, but we cannot show multiple records in a table. Tables will only have a single value in each column. So when they say "allow multiple", we will need to:
The original "artist" table will not have any columns added to it at all, so I'm not sure it makes sense to have the "Allow Multiple" option attached to a column. |
Beta Was this translation helpful? Give feedback.
-
@kgodey Adding Summary ColumnsThe user will have the option to add any available column to a view. In this case, 'releaseName' was initially added by creating a view from the 'release' table first. Once create the user added the second column 'trackName' from the 'track' table. Editing a Summary RecordWhen the user wants to edit, they can choose to remove any of the records. Which will remove the matching row from the 'release_track' table. Or they can choose to add an additional record. Which should swap the list of records for a form in which the user can define the new pair. Deleting a Mapping TableIf the mapping table is deleted, the summary column will remain in the view but will go back to being blank. QuestionsIf the view has multiple columns, let's say there's an 'artistName' column and a 'releaseName' column and both are linked by foreign key.
So now I add 'trackName', which could result in two different mapping tables:
Do we create both, or does the user only map to one of the fields? |
Beta Was this translation helpful? Give feedback.
-
@kgodey @pavish |
Beta Was this translation helpful? Give feedback.
-
@kgodey @pavish Thanks for your comments
Please see the attached video for a demonstration: If this makes sense I will finalize the design and update the specs. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Based on the new action plan from the 2021-10-15 meeting, we're going to update the requirements for issues in the milestone. I'm marking this discussion done, we'll start new discussions for further updates. |
Beta Was this translation helpful? Give feedback.
-
The design for issue #443 is ready for review. Please follow the Review Guidelines and make sure to review before the set deadline expires.
Document
https://wiki.mathesar.org/en/design/specs/multiple-records-spec
Reviewers
@kgodey @pavish @mathemancer Your review is required.
Feedback from the community is also welcome. Contributors can find more context about Mathesar's design strategy here.
Deadline
The deadline for submitting feedback is set for next week, on on Tuesday 28th.
Beta Was this translation helpful? Give feedback.
All reactions