Choose your database:
AnySQL
MySQL
MS SQL Server
PostgreSQL
SQLite
Firebird
Oracle
SQL Anywhere
DB2
MaxDB

Subscribe to our news:
Partners
Testimonials
Stephen Arrowel, Database Administrator: "We are in the process of implementing Firebird solutions at multiple levels in our international organization. We expect that SQL Maestro Group will do nothing short of revolutionize the way we develop and maintain our Firebird databases. The continuous improvement and development means that the product is extremely flexible and will grow with us. The service and responsiveness of the Support Team has been exceptional. They have devoted countless hours to understanding our needs, so that we could get a Firebird administration tool which would be so simple and effective in use. SQL Maestro Group is helping Sytrax sail into the 21st Century".
Neil McPherson: "Thanks very much for your advice. I would just like to add that SQL Maestro makes life so much easier to work with Firebird, I have tried some of the other management tools but Maestro is such a nicely organized product and it has never let me down".

More

Add your opinion

Firebird Maestro online Help

Prev Return to chapter overview Next

Database Trigger Editor

Database Trigger Editor can be opened automatically after the trigger is created and is available on editing (see Editing Triggers for details).

 

The basic principles of Object Editors in Firebird Maestro are considered in the corresponding topic. See below to find the description of editor tabs that are unique to the current object.

 

Database Trigger Editor provides you with an ability to edit trigger properties. The Properties tab allows you to change the trigger name, the trigger definition, and the trigger events.

Name

Use the field to rename the database trigger.

 

Active

Check the option to enable the trigger.

 

Event

Use the field to change the database trigger event:

 

CONNECT

Database connection established
A transaction is started
Triggers are fired - uncaught exceptions rollback the transaction, disconnect the attachment and are returned to the client
The transaction is committed

DISCONNECT

A transaction is started
Triggers are fired - uncaught exceptions rollback the transaction, disconnect the attachment and are swallowed
The transaction is committed
The attachment is disconnected

TRANSACTION START

Triggers are fired in the newly user created transaction - uncaught exceptions are returned to the client and the transaction is rolled-back.

TRANSACTION COMMIT

Triggers are fired in the committing transaction - uncaught exceptions rollback the triggers savepoint, the commit command is aborted and the exception is returned to the client.
Note: for two-phase transactions the triggers are fired in "prepare" and not in commit.

TRANSACTION ROLLBACK

Triggers are fired in the rolling-back transaction - changes done will be rolled-back together with the transaction and exceptions are swallowed.

 

 

To apply the changes, select the Apply Changes item in the Navigation bar or use Ctrl+F9 or Ctrl+F7 shortcut keys.

 

It is also possible to modify object properties without opening the object editor: use the Object Properties item of the popup menu of the selected object from the explorer tree.



Prev Return to chapter overview Next