> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/server/server-usage/triggers-events/triggers/trigger-limitations.md).

# Trigger Limitations

The following restrictions apply to [triggers](/docs/server/server-usage/triggers-events/triggers.md):

* All of the restrictions listed in [Stored Routine Limitations](/docs/server/server-usage/stored-routines/stored-routine-limitations.md).
* All of the restrictions listed in [Stored Function Limitations](/docs/server/server-usage/stored-routines/stored-functions/stored-function-limitations.md).
* Triggers are always executed for each row. MariaDB does not support the standard `FOR EACH STATEMENT` option.
* Triggers cannot operate on any tables in the mysql, `information_schema` or `performance_schema` database.
* Cannot return a result set.
* The [RETURN](/docs/server/reference/sql-statements/programmatic-compound-statements/return.md) statement is not permitted, since triggers don't return any values. Use [LEAVE](/docs/server/reference/sql-statements/programmatic-compound-statements/leave.md) to immediately exit a trigger.
* Triggers are not activated by [foreign key](/docs/server/ha-and-performance/optimization-and-tuning/optimization-and-indexes/foreign-keys.md) actions.
* If a trigger is loaded into cache, it is not automatically reloaded when the table metadata changes. In this case a trigger can operate using the outdated metadata.
* By default, with row-based replication, triggers run on the master, and the effects of their executions are replicated to the slaves. It is possible to run triggers on slaves. See [Running triggers on the slave for Row-based events](/docs/server/ha-and-performance/standard-replication/running-triggers-on-the-replica-for-row-based-events.md).

## See Also

* [Trigger Overview](/docs/server/server-usage/triggers-events/triggers/trigger-overview.md)
* [CREATE TRIGGER](/docs/server/server-usage/triggers-events/triggers/create-trigger.md)
* [DROP TRIGGER](/docs/server/reference/sql-statements/data-definition/drop/drop-trigger.md)
* [Information Schema TRIGGERS Table](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-triggers-table.md)
* [SHOW TRIGGERS](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-triggers.md)
* [SHOW CREATE TRIGGER](/docs/server/reference/sql-statements/administrative-sql-statements/show/show-create-trigger.md)

<sub>*This page is licensed: CC BY-SA / Gnu FDL*</sub>

{% @marketo/form formId="4316" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mariadb.com/docs/server/server-usage/triggers-events/triggers/trigger-limitations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.