Hi,
I'm using a TIBCQuery assigned to TIBCScript.DataSet for better control over what's executed in the script.
In the AfterExecute event I check for the statement type (.SQLType property) and if it's a SQL_COMMIT, I make it visually clear that the transaction has committed.
However, the AfterExecute is never fired for a COMMIT in a Script.
Is this a bug?
With regards,
Martijn Tonies
Upscene Productions
Executing a COMMIT in TIBCScript.DataSet does not fire event
COMMIT, ROLLBACK and START TRANSACTION are perfectly valid commands inside any InterBase/Firebird script, the Script component should support this and if you supply a method of executing in a DataSet, at least the AfterExecute should fire (even though it does not actually use that to execute the COMMIT) so I know it has executed a COMMIT.Plash wrote:TIBCScript executes some statements without using DataSet. For transaction control commands the TIBCScript component calls the corresponding methods of TIBCTransaction.
I cannot use the methods of TIBCTransaction in this case.
As an alternative, could you add events to TIBCTransaction for OnCommit/OnRollback/OnStart ?Plash wrote:Currently TIBCQuery does not support the transaction control commands and create/drop database commands. So script executes these commands without using TIBCQuery.
We'll consider the possibility of supporting these commands in TIBCQuery, but that is hardly to happen in the nearest future.
That way, I could work around the issue.