Yes I agree also that's a way to do it. I was just trying to avoid
having a 'special' way of doing things, but I suppose the others teams
will have to comply & adapt their programs if they want to act on this
Thanks to all for your input(s)
> How about a procedure that does the "delete" for you - instead of
> DELETE FROM table, create a procedure DELETE_table with parameters
> with the primary key value. This way, you're keeping the delete logic
> in the database... Next, create a BEFORE DELETE trigger that raises
> an exception along the lines of "cannot delete, use stored procedure
> So instead of doing a DELETE FROM, you need to call the procedure.
> The trigger with the exception ensures no-one is actually deleting
> With regards,
> Martijn Tonies
> InterBase Workbench - the developer tool for InterBase & Firebird
> Firebird Workbench - the developer tool for Firebird
> Upscene Productions
> "This is an object-oriented system.
> If we change anything, the users object."