Hmm we may be talking about different things here.
I need to delete from this table otherwise staff allocation will get messed up. I don't understand when you say:
>>In order to accurately track employee responses and activities (along with work history) within a company or organization, it would be best to NOT delete them from the intersection table, because then you will also have to UPDATE the TICKETS table.
<<
This isn't the departments table....that is a seperate table. The allocation table is just for determining which staff member has access to which department. So if admin remove access from one department then I need to delete that row to stop the user seeing the tickets.
Also I don't need LEFT JOIN as the user record is always accessible as a hashref, $USER so I can just use WHERE
I need to delete from this table otherwise staff allocation will get messed up. I don't understand when you say:
>>In order to accurately track employee responses and activities (along with work history) within a company or organization, it would be best to NOT delete them from the intersection table, because then you will also have to UPDATE the TICKETS table.
<<
This isn't the departments table....that is a seperate table. The allocation table is just for determining which staff member has access to which department. So if admin remove access from one department then I need to delete that row to stop the user seeing the tickets.
Also I don't need LEFT JOIN as the user record is always accessible as a hashref, $USER so I can just use WHERE