Triggers in different schemas can have the same name.
Still, performing these operations on a live database is potentially risky and should only be done with the utmost care.
bulk import operations are forced to backup and restore much more often then needed.
Since changes to triggers don't imply structural changes to the table itself, Firebird no longer increments the table change counter when In Firebird 2.0 only, a restriction is in place which prevents anyone from dropping, altering or recreating a trigger or stored procedure if it has been used since the database was opened.
PDF (US Ltr) - 37.9Mb PDF (A4) - 38.0Mb PDF (RPM) - 37.3Mb HTML Download (TGZ) - 10.3Mb HTML Download (Zip) - 10.3Mb HTML Download (RPM) - 8.9Mb Man Pages (TGZ) - 216.8Kb Man Pages (Zip) - 329.6Kb Info (Gzip) - 3.4Mb Info (Zip) - 3.4Mb My SQL Backup and Recovery My SQL Globalization My SQL Information Schema My SQL Installation Guide My SQL and Linux/Unix My SQL and OS X My SQL Partitioning My SQL Performance Schema My SQL Replication Using the My SQL Yum Repository My SQL Restrictions and Limitations Security in My SQL My SQL and Solaris Building My SQL from Source Starting and Stopping My SQL My SQL Tutorial My SQL and Windows My SQL NDB Cluster 7.5 If you drop a table, any triggers for the table are also dropped.
Trigger names exist in the schema namespace, meaning that all triggers must have unique names within a schema.
*/ if update (title_id) and datename(dw, getdate()) in ("Saturday", "Sunday") begin rollback transaction print "We do not allow changes to " print "primary keys on the weekend." end.