23 create events and tickets #24
Merged
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
lgmfred
force-pushed
the
23-create-events-and-tickets
branch
from
9014eec
to
3e3712d
Compare
MICHAELMUNAVU83
requested changes
Oct 11, 2023
There was a problem hiding this comment.
Hey @lgmfred , Nice work , I have left a review , all that is required is for you to add a column to the ticket_types table called number .
lgmfred
force-pushed
the
23-create-events-and-tickets
branch
from
0c41bf9
to
2e55d86
Compare
MICHAELMUNAVU83
approved these changes
Oct 11, 2023
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.
Hey folks,
@MICHAELMUNAVU83 There's really nothing in this PR yet (well, besides a sad attempt at the Events LiveView templates). I'm trying to play around with the events and tickets relationship defined(#23) but I've to admit we didn't do much in the DB design session we had.
This is the only thing we came up with about events and tickets. Did we mean to define a ticket here or a ticket type for an event?
I believe each event is supposed to define its own ticket type and prices, or are we going to assume all events will have the same ticket types?
Also, how best can we define the relationship between an event and its ticket types in the DB? Will ticket types and prices be stored in a field on the event table or in a different table(s)? If in a field, in which format?
Sorry, my SQL knowledge is very minimal and clarification on this would make this just a bit simpler. Thanks