Configure SpringBoot entities to reflect database constraints

sanger96 / Happenings_Team-5_UTD_Senior_Design_Project

UTD Senior Design Project; Group Members: Gaurav Sanger, Jonathan Lam, Robert Dohm, Landin Kasti, Charles Eaton

3 stars 0 forks source link

Configure SpringBoot entities to reflect database constraints #55

Open LKASTI opened 5 months ago

LKASTI commented 5 months ago

There are several changes that need to be made to entity files to reflect database constraints and improve readability. These are some of the changes that I thought might be necessary:

[x] Adding name field to Club entity
[x] Adding unique value constraints on...
- [x] Event name
- [x] Event photoSubDirectory
- [x] Club name
- [x] Interest name
[ ] Delete constraint to event after [ ] time passed from end datetime
[x] Event cascading delete on an Appointment, and Location should be deleted once event has been deleted
[x] Club cascading delete on any associated Events

(Any other necessary changes to be discussed)

LKASTI commented 5 months ago

[x] removed latitude, longitude, and buildingfields from the Location class

This means the addOrOmit method in the location controller must be edited

LKASTI commented 5 months ago

All listed constraints were applied except for deleting an event after certain time passed from event taking place. I did more research into this topic and found that this scenario might require additional scheduling methods for checking when an event has started, ended, and when it can be deleted.

link1, link2 - add non-persistent boolean field to an event to check if it ended

how will we know when an event starts/ends?

adding a scheduling method that checks every minute to see if an event has started seems bad
scheduling method will happen every [ ] amount of time and retrieves all events that occurred, then deletes those events where the elapsed time after the event’s end time is ≥ [ ] amount of time

Edit: This comment refers to the newly created issue #70

LKASTI commented 5 months ago

TODO: Forgot about not null constraints. Those need to be added to necessary fields...

LKASTI commented 5 months ago

Null-able constraint annotations added to relevant fields. More constraints can be added, such ensuring Appointment end times occurring after start times, the interval of time between the start and end time must be at least [ ] amount of time, and any other constraints needed.