Sorry for annoying with a possibly stupid question, but why does this statement:
ALTER TABLE SESSION_LOGGING disable CONSTRAINT fk_session_log_ben_name;
work perfectly fine and just like expected, when executed as a normal SQL command, but when placed in an otehrwise correct working TRIGGER (which is NOT executed for the session_logging table!), causes the trigger not to be able to compile anymore?
Hope someone can help...</div