That's the only way we've figured out to do it. Brad. > From: Jeffrey Butera <[email protected]> > To: U2 Users List <[email protected]> > Date: 10/10/2011 10:39 AM > Subject: [U2] Finding Triggers on files > Sent by: [email protected] > > Unidata 7.2.9 on RedHat > > Is there a programmatic way to determine if a file has a trigger on it? > I've looked at FILEINFO and it doesn't indicate that any parameter would
> return trigger information. I know I can do something like: > > EXECUTE "LIST.TRIGGER MY_FILE" CAPTURING X.RESULT > > and parse X.RESULT, but was curious if there's a better way. > > I've occasionally been bitten by converting a file from static to > dynamic hashing, losing an update trigger in the process so I want to > write some code to check these and let me know if something's awry. > > -- > Jeff Butera, Ph.D. > Manager of ERP Systems > Hampshire College > [email protected] > 413-559-5556 > > "...we must choose between what is right and what is easy..." > Dumbledore > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users U.S. BANCORP made the following annotations --------------------------------------------------------------------- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. --------------------------------------------------------------------- _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
