Re: Obtaining the complete code for a trigger from systrigbody

> > Yes, I understood that. I just don't understand how querying the catalog addresses > this problem better than using dbschema. How often do you expect to run your > catalog query? Will your program then automatically alter (drop/create) the trigger > to add your new trigger logic? Given that a third party can make changes to the > triggers, can you reliably automate the addition of new logic? > > It still seems to me that you could just as easily capture the output of dbschema > and programatically parse it or manually edit it, then run it through dbaccess. > Well, querying the system catalog would lead me to obtaining the code I wanted to incorporate, using dbschema will lead me with another things I don't want, create table, create index, more than just the trigger I want, but your idea helped, I will get use dbschema and obtain the specific trigger I want programmaticaly as you told. I will run it once a month and the program will drop the existing trigger and recreate it using the existing logic, more the one I added. Thanks, -- Ricardo Palmeira mailto:palmeira@tce.pe.gov.br