Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread TDBISAMEngine triggers and memory tables
Thu, May 16 2013 8:53 PMPermanent Link

ClockOn

Hi

We currently have auditing processing on the database using the triggers in the DBISAMEngine, which are working fine and have been for quite a while but I have just realised that it is treating memory tables the same way.

So my question is is there a way to determine if the table passed through is a memory table. I can see a simple way is to formulate a naming convention for our memory tables but that requires going over and restructuring a bit so im trying to avoid this.

As an example we have the table "Employee" if we need to create memory version we would probably call it "\memory\Employee" so when passed we cannot tell the difference.

procedure TDBISAMAudits.DoOnAfterInsert(Sender: TObject; TriggerSession: TDBISAMSession; TriggerDatabase: TDBISAMDatabase;
 const TableName: string; CurrentRecord: TDBISAMRecord);


hope that makes sense...
Fri, May 17 2013 4:19 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

ClockOn


Simply check the database - if its Memory its an in-memory table.

Roy Lambert [Team Elevate]
Wed, May 22 2013 8:13 PMPermanent Link

ClockOn

lol thanks Roy

*slap to forehead...
Image