Ken�z Attila wrote: > Hi! > > I need the history of some tables in my database. I wrote a quite simple > program that generates (and executes) the creation code of the history > table and the trigger for a (original) table. The problem is that some > cases I need some extra code to run in the trigger. For these cases I > figured out that I would use some standard database procedure name (for > example: reserved_clients_trigger_ai for the code that I need to run in > the clients table's after insert trigger). The program would look if there > is a dbproc called like this in the catalog, and if there is, then it > would generate the call of the procedure in the trigger. Now I give the id > of the inserted (or updated) row for the dbproc, but in this case I cannot > reach the old.<..> values in the procedure. Is there any possibility to > give the :old and the > :new as records to a database procedure? If not, is there some other > :simple > solution for my problem? (I do not want to use - if it is possible - > dbprocs that has too times many parameters as many columns the tables > have: one for each old value and one for each new value.) > > Thanks: > Attila Kenez
one could use a temp table i suppose. -- John Holland [EMAIL PROTECTED] _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
