Create SessionDate model #1830
Merged
Create SessionDate model #1830
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thomasleese
force-pushed
the
create-session-dates
branch
from
2cc37ac
to
16c9f42
Compare
thomasleese
force-pushed
the
create-session-dates
branch
from
16c9f42
to
aa96fec
Compare
thomasleese
force-pushed
the
create-session-dates
branch
from
aa96fec
to
ff8ce5f
Compare
This adds a model which will capture the dates for a particular session, it's a one-to-many relationship with a unique constraint on the session and date value. This will eventually replace the single date column on sessions as the latest designs have sessions across multiple dates.
thomasleese
force-pushed
the
create-session-dates
branch
from
ff8ce5f
to
69d6851
Compare
|
tvararu
approved these changes
Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a model which will capture the dates for a particular session, it's a one-to-many relationship with a unique constraint on the session and date value.
This will eventually replace the single date column on sessions as the latest designs have sessions across multiple dates.