Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 3 of 3 total |
TDBISAMEngine triggers and memory tables |
Thu, May 16 2013 8:53 PM | Permanent 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 AM | Permanent Link |
Roy Lambert NLH Associates 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 PM | Permanent Link |
ClockOn | lol thanks Roy
*slap to forehead... |
This web page was last updated on Friday, April 19, 2024 at 07:09 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |