Now that sounds like a very cool approach! Sent from my iPhone
On Oct 6, 2013, at 1:51 PM, "A. Razzak Memon" <[email protected]> wrote: > At 12:59 PM 10/6/2013, Mike Byerley wrote: > >> Why not. Otherwise your choice is to update the dataset AFTER a save to >> disk. I can't say definitively that either approach is less time consuming >> to construct, so.... > > In addition, to automate the entire process, once the record is INSERTed > or UPDATEd, you could take advantage of AFTER INSERT and AFTER UPDATE > TRIGGERs in R:BASE eXtreme 9.5. > > In such scenario, you will have to first define/debug a procedure (Stored > Procedure) that will trigger the specific code AFTER a row is INSERTed or > AFTER a row is UPDATEd. > > Before Insert Trigger: > Executes the specified stored procedure before a row is inserted > > After Insert Trigger: > Executes the specified stored procedure after a row is inserted > > Before Update Trigger: > Executes the specified stored procedure before a row is updated > > After Update Trigger: > Executes the specified stored procedure after a row is updated > > Before Delete Trigger: > Executes the specified stored procedure before a row is deleted > > After Delete Trigger: > Executes the specified stored procedure after a row is deleted > > Very Best R:egards, > > Razzak. > > www.rbase.com > www.facebook.com/rbase > -- > 30+ years of continuous innovation! > 15 Years of R:BASE Technologies, Inc. making R:BASE what it is today! > -- >
