![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 6 of 6 total |
![]() |
Tue, Jul 31 2007 5:16 AM | Permanent Link |
Tomas | Hi,
Does trigger events executed on server? If yes, then which trigger event executed first, client or server(client - dbisam dataset which is connected to server)? BeforeInsertTrigger AfterInsertTrigger BeforeUpdateTrigger AfterUpdateTrigger BeforeDeleteTrigger AfterDeleteTrigger Regards, Tomas |
Tue, Jul 31 2007 8:39 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Tomas,
<< Does trigger events executed on server? >> Yes. << If yes, then which trigger event executed first, client or server(client - dbisam dataset which is connected to server)? >> The trigger events only execute on the server for remote sessions - they do not execute on the client at all in such a situation. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Aug 1 2007 2:48 AM | Permanent Link |
Tomas | <<< If yes, then which trigger event executed first, client or
server(client - dbisam dataset which is connected to server)? >> The trigger events only execute on the server for remote sessions - they do not execute on the client at all in such a situation.>> That is not good in my situation. I can't find any other methods which could notify about Insert/Delete/Edit in both situations - dataset and sql. Is it possible always execute triggers on client side? Regards, Tomas |
Wed, Aug 1 2007 2:05 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Tomas,
<< That is not good in my situation. I can't find any other methods which could notify about Insert/Delete/Edit in both situations - dataset and sql. Is it possible always execute triggers on client side? >> Unfortunately, no. The client's remote session doesn't even know how the insert is occurring, which is essential for properly handling the trigger. It's simply making a request to insert a row. Why do you need the client notification ? Also, have you considered just using the TDataSet BeforePost/AfterPost events for this pupose on the client side ? -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Aug 1 2007 5:15 PM | Permanent Link |
Aage Johansen | Tim Young [Elevate Software] wrote:
> Tomas, > > << That is not good in my situation. I can't find any other methods which > could notify about Insert/Delete/Edit in both situations - dataset and sql. > > Is it possible always execute triggers on client side? >> > > Unfortunately, no. The client's remote session doesn't even know how the > insert is occurring, which is essential for properly handling the trigger. > It's simply making a request to insert a row. > > Why do you need the client notification ? Also, have you considered just > using the TDataSet BeforePost/AfterPost events for this pupose on the client > side ? > When is the trigger triggered... If a rollback is performed, a notification in the BeforePost/AfterPost may not be what he wants. (I have not used events with dbISAM/EDB so this may be completely off the mark - I expect database triggers to get fired at commit time) -- Aage J. |
Fri, Aug 3 2007 1:14 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Aage,
<< When is the trigger triggered... If a rollback is performed, a notification in the BeforePost/AfterPost may not be what he wants. >> I understand, but the normal trigger events won't fire in the case of a rollback anyways. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |