> So, yes, I'd do this at an application level... although I have no idea what
> triggers are :)
>
It does pretty much the same, only at the database level. The
application doesn't have to know. All the application needs to know is
to delete the id in the 'employee' table. Triggers will do the re
on 26/11/02 3:46 PM, Faisal Abdullah ([EMAIL PROTECTED]) wrote:
> Lets say I have a table called 'employees', and another table called
> 'training_history'.
>
> Lets say I need to delete an employee, I would also have to delete his
> record in the 'training_history' table.
The employee would (I
Hi guys,
Lets say I have a table called 'employees', and another table called
'training_history'.
Lets say I need to delete an employee, I would also have to delete his
record in the 'training_history' table.
Which is the best way to go about this? Controlling it at application
level? Or should
3 matches
Mail list logo
