🏆 Replace DB trigger by application handler for the timestamp columns

[RMCampos]

User Story

As a user, I want to know that all timestamp columns are being handled by the application, not by triggers.

Acceptance Criteria

• Create a SQL migration file for:
  • Dropping trigger set_entry_timestamp from all tables;
  • Dropping trigger set_update_timestamp from all tables;
  • Dropping both trigger_set_entry_timestamp and trigger_set_update_timestamp procedures from the Postgres database;
• Add @PrePersist routines (on all table Entities Java classes) ensuring both entry_timestamp and current_timestamp will get updated accordingly.

References

• PostgreSQL DROP TRIGGER Statement: https://www.postgresqltutorial.com/postgresql-triggers/postgresql-drop-trigger/
• How to use @PrePersist and @PreUpdate: https://vladmihalcea.com/prepersist-preupdate-embeddable-jpa-hibernate/

[RMCampos]

Updates:

• No need to add manual handlers for both entry and update seedlot timestamps, because all child tables are being handled by the Audit Information Class which contains and handles these columns.
• Only the Favourite Activities table was required to be manually handled.