(General) Grouping Rereleases #66

Open
opened 2024-03-06 22:05:24 +00:00 by boiii · 0 comments
Collaborator

A scene may be (re)released on multiple channels.

Grouping scenes would allow showing that a single scene has been released on multiple channels.

Possible implementation

  • Create a new table MasterRelease
  • Create a nullable, indexed foreign key from Release to MasterRelease (relation: release.master_release_id -> master_release.id)
  • To get a list of (re)releases of a release (X), just do
SELECT *
FROM releases
WHERE master_id = X.master_id
    AND id != X.id
A scene may be (re)released on multiple channels. Grouping scenes would allow showing that a single scene has been released on multiple channels. ### Possible implementation - Create a new table `MasterRelease` - Create a nullable, indexed foreign key from `Release` to `MasterRelease` (relation: release.master_release_id -> master_release.id) - To get a list of (re)releases of a release (X), just do ```sql SELECT * FROM releases WHERE master_id = X.master_id AND id != X.id ```
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: DebaucheryLibrarian/traxxx#66
No description provided.