Deprecated: Joomla\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 41

Deprecated: Return type of Joomla\Input\Input::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 170

Deprecated: Joomla\CMS\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Input.php on line 31

Deprecated: Joomla\CMS\Input\Cookie implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Cookie.php on line 21

Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Uri/Uri.php on line 141
Issue Tracker Guide :: Triggers

Deprecated: F0FInput implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/f0f/input/input.php on line 35

Deprecated: Joomla\CMS\Input\Files implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Files.php on line 21

Triggers

A database trigger is procedural code that is automatically executed in response to certain events on a particular table or view in a database. The trigger is mostly used for maintaining the integrity of the information on the database. For example, when a new record (representing a new worker) is added to the employees table, new records should also be created in the tables of the taxes, vacations and salaries.

Triggers List

The triggers list display shows the database table triggers created by the component.

It does not show any triggers created by another mechanism, unless they happen to contain the specific string 'audit' within their name.

Triggers are names after the table upon which they are applied, followed by the specific string '_audit_' and then by a two character string, the first of which indicates whether it is a 'BEFORE' (b) or 'AFTER' (a) trigger, and the second indicates whether it is applied on an 'INSERT' (i), 'UPDATE' (u) or 'DELETE' operation.'

The screen also allows a single point where triggers may be enabled, which is where the trigger is created within the database. Disabling the trigger removes the trigger from the database.

[Important]Important

MySQL has a few restrictions upon triggers which may be briefly summarised as follows: Only one trigger of any specific type is possible upon any given table. Triggers if present are automatically enabled. Triggers can not be disabled. Disabling a trigger requires the trigger be deleted.

The screen can also used to delete triggers. Deletion of a trigger not only removes it from the database (disabling), but also removes all trace of the trigger from the component.

Figure 5.3. Triggers List

Triggers List

Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries