Database Refactor

[nelsontr]

In our database, we have a bunch of tables that have different contexts. For example, elections and options are only use for online voting, theses and areas are only used when acessing Thesys Master (not working). A new database infrastructure should be implement in order to take advantage of schemas and to centralize a user information in one specific table (now, the email and name are present in members table and other relevant information in collabs).

[nelsontr]

Something like this:

Done with https://dbdiagram.io NN - Not Null, Serial - Integer automatically calculated and incremented according to last record,

Necessary:

• SQL Function to delete memberNotifications when renewed or when member becomes a non-member (already implemented)
• SQL Function to delete renewStartDate and renewEndDate on non-members (can be determined by electorDate)

[nelsontr]

Current State:

Lack of schemas; Lack of necessary Foreign Keys; Lack of Data Structure Organization