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

Subscribe to our news:
Partners
Testimonials
Andrey Bistriy: "In our daily business we face the database management and refactoring. We were pleasantly surprised to discover SQL Maestro. After trying it out we started to use it on a regular basis".
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".

More

Add your opinion

Customers
Download Buy

Firebird Maestro online Help

Prev Return to chapter overview Next

Create Database Trigger Wizard

Create Database Trigger Wizard guides you through the process of creating a new trigger. See How To Create Database Trigger for instructions on running this wizard. Only database owner and SYSDBA can do database triggers DDL.

 

 

The basic principles of Create Object Wizards in Firebird Maestro are covered by the corresponding topic. See below to find the description of wizard steps that are unique to the current object.

 

The wizard step was supplied to define common database trigger properties.

 

Name

The field represents the new database trigger name as it was set on the previous wizard step.

 

Comment

Enter some words to comment the database trigger or leave it blank.

 

Active

Check the option to enable the trigger.

 

Event

Use the popup menu to select the new 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.

 

 

Specifying trigger definition

Use this step to specify the trigger steps to be executed when the trigger fires. You can also do it later using non-modal editor.



Prev Return to chapter overview Next