If a user generates print jobs, they will start in the "Held" status. If the user is then deleted, those held print jobs remain and cannot be printed. We should cascade the delete using a foreign key constraint. There is no practical reason to keep the existing behavior.
If a user generates print jobs, they will start in the "Held" status. If the user is then deleted, those held print jobs remain and cannot be printed. We should cascade the delete using a foreign key constraint. There is no practical reason to keep the existing behavior.