I want to log all database changes to a logging table within the Database

Acceptance Criteria

• New Database Tables
  • Events
    • Event_Id - ID of the event
    • Event_Name - VARCHAR name of the event
  • Logs
    • Log_Id - ID of the log
    • Event_Id - ID of the event
    • User_Id - ID of the user which triggered the event
    • Log_Details - VARCHAR with the higher details of the event
    • Log_Date_Time - DATETIME of the event
• New Example Data
  • Different Events which may be called throughout running of the site
• New Classes
  • Events Entity and Repo
  • Logs Entity and Repo
  • LoggingMethods Service
• New Methods
  • LoggingMethods.CreateNewLog(Event, Session, Details)
• New Functionality
  • Call to the "LoggingMethods.CreateNewLog(Event, Session, Details)" method whenever a database update is made
    • Will decide whether to insert the event using the Id of a normal user of "SuperAdmin" based on which value is present

Tracking Data

Stage	Date
Entered Open at	2021-12-06 16:55:00
Entered Ready at	2021-12-09 11:15:00
Entered Dev at	2021-12-09 11:15:00
Entered Test at	N/A
Entered Done at	2021-12-10 13:34:00
Entered Closed at	2021-12-10 13:34:00

Definition of Ready

• Issue is populated with relevant Acceptance Criteria
• Issue name meets the format “As a I want so that ”
• Issue is not dependant on any, non-closed, issue
• Issue appropriately weighted based on team opinions and planning poker session(s)
• If issue has a corresponding UI element, it has a “UI Plan” created before development begins
• If Issue has a corresponding DB element, it has an ER Diagram created with corresponding changes before development begins
• All above points verified by a member of the team external to the main developer(s) of the issue

Definition of Done

• At least one automated test per major feature created during the process of the issue
• All acceptance criteria complete and met
• All relevant tests pass
• Appropriate Javadoc present throughout
• All above points verified by a member of the team external to the main developer(s) of the issue