Remove end date #208
Merged
Remove end date #208
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
tommyneu
force-pushed
the
remove-end-date
branch
from
ac95f09 to
0c82ce4
Compare
|
SQL conversion script was tested and confirmed working on events-dev.unl.edu with the version of mariaDB running on the server |
tommyneu
force-pushed
the
remove-end-date
branch
from
3ac5d65 to
320f25b
Compare
|
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.
The current way data is being created and stored has led to some sorting issues where ongoing events are being sorted before any other events in a list of events.
The best solution we have come up with to resolve the issues is to remove the end date and force on going events to be daily recurring instead. This would mean no single event occurrence would last more than 24 hour.
This also lets us update the time input fields and add a new column for time modes where more information about the timings of the event occurrence can be stored.