Always ensure that any file opens in triggers resolve to specific paths or accounts - that quick and dirty q-pointer from the 'wrong' account will get you if you don't.
You can't debug through triggers (because they run in a transaction). We also use a 'sub' trigger system but call @subroutines instead of reading a table. No performance issues. >-----Original Message----- >We are getting ready to implement triggers on a universe system running >under Windows Server 2003. I created a trigger and tested it out and it >appears to do exactly what we need. My question is are there any gotchas or >issues we should be concerned about with triggers? Are there any >performance issues that anyone has seen related to triggers? ********************************************************************** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this communication in error, please reply to this e-mail to notify the sender of its incorrect delivery and then delete it and your reply. It is your responsibility to check this email and any attachments for viruses and defects before opening or sending them on. Spotless collects information about you to provide and market our services. For information about use, disclosure and access, see our privacy policy at http://www.spotless.com.au Please consider our environment before printing this email. ********************************************************************** ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
