> 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/event-scheduler/event-limitations.md).

# Event Limitations

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

* All of the restrictions listed in [Stored Routine Limitations](/docs/server/server-usage/stored-routines/stored-routine-limitations.md).
* Events cannot return a result set.
* Event names are case insensitive, so it's not possible to define two events in the same database if their case insensitive names will match. This restriction has applied since MariaDB/MySQL 5.1.8. If you are upgrading from an older version of MySQL, and have events that could clash, these events need to be renamed before the upgrade.
* Events do not support dates beyond the maximum that can be represented in the Unix epoch (2038-01-19).
* Events cannot be created, dropped or altered by another stored program, trigger or event.
* Events cannot create, drop or alter stored programs or triggers
* Event timings cannot be strictly predicted. The intervals `MONTH`, `YEAR_MONTH`, `QUARTER`, and `YEAR` are all resolved in months. All others are resolved in seconds. A delay of up to two seconds is possible in extreme cases, and events scheduled to run at the same second cannot be executed in a given order. The `LAST_EXECUTED` column in the [INFORMATION\_SCHEMA.EVENTS](/docs/server/reference/system-tables/information-schema/information-schema-tables/information-schema-events-table.md) table will however always be accurate to within a second.
* A new connection is used for each execution of statements within the body of an event, so the session counts for [server status variables](/docs/server/server-management/variables-and-modes/server-status-variables.md) such as `Com_delete` and `Com_select` will not reflect these.
* Because the Event Scheduler depends on grant tables for its functionality, it is automatically disabled when the server is running with [--skip-grant-tables](/docs/server/server-management/starting-and-stopping-mariadb/mariadbd-options.md#-skip-grant-tables).

<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/event-scheduler/event-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.