To enable MySQL event scheduler, 1. Use SHOW VARIABLES LIKE 'event_scheduler'; view the status; 2. If OFF, add event_scheduler=ON in the configuration file or run SET GLOBAL event_scheduler = ON; Create Event Example: Update the "to be paid" order status for more than 30 days at 2 a.m. every day to "cancel", statements include the specified name, execution frequency, start time, and SQL to be executed; manage Events include SHOW EVENTS, modify ALTER EVENT, and delete DROP EVENT; Notes include permission requirements, low risk of SQL injection, no retry for failure, possible shutdown after restart, and multiple events No conflict but requires concurrency.
MySQL's event scheduler is a very practical feature that automatically performs certain SQL operations at a specified time. It's a bit like Linux's cron job, but it's fully integrated inside the database. If you need to clean up data, generate reports, or update status regularly, event scheduler can come in handy.

How to enable MySQL event scheduler
By default, MySQL's event scheduler may be turned off. To use it, first make sure event_scheduler
is enabled.
You can check the current status through the following command:

SHOW VARIABLES LIKE 'event_scheduler';
If the return is OFF
, it needs to be turned on manually. You can add it in a configuration file such as my.cnf or my.ini:
[mysqld] event_scheduler=ON
Or run directly in MySQL:

SET GLOBAL event_scheduler = ON;
Note: The temporary setting is only valid for the current session and is invalid after restart. It is recommended to modify the configuration file to persist settings.
Create a simple Event example
Suppose you have an order table orders
with a field status
, and you want to mark "to be paid" orders for more than 30 days as "cancelled" at 2 a.m. every day.
The statement that creates an event is roughly like this:
CREATE EVENT daily_order_cleanup ON SCHEDULE EVERY 1 DAY STARTS TIMESTAMP(CURRENT_DATE) INTERVAL 2 HOUR DO UPDATE orders SET status = 'cancelled' WHERE status = 'pending' AND created_at < NOW() - INTERVAL 30 DAY;
Explain a few key points:
-
daily_order_cleanup
is the name of this event. -
EVERY 1 DAY
means execution once a day. -
STARTS ...
set the time for the first execution, here is 2 am today. - Following
DO
is the SQL statement you want to execute.
After setting this up, MySQL will automatically run this update statement for you at 2 a.m. every day.
View and manage Events
You can use the following command to view the event you have created:
SHOW EVENTS FROM your_database_name;
If you want to modify an event, such as adjusting execution time or SQL content, you can delete it first and then recreate it, or use the ALTER EVENT
command.
For example, if you want to change this event to be executed once a week:
ALTER EVENT daily_order_cleanup ON SCHEDULE EVERY 1 WEEK;
Deleting an event is also very simple:
DROP EVENT IF EXISTS daily_order_cleanup;
Notes and FAQs
- Permissions issue :
EVENT
permission is required to create an event. If not, an error may be reported. - SQL injection risk? Don't worry, the event is written with static SQL, which will not involve user input injection issues.
- What should I do if the event execution fails? If there is an error in SQL inside, event will not try again by default. You can check it in combination with the log.
- What should I do if the event is disabled? Sometimes event_scheduler may be turned off after the server restarts. Remember to check the status.
- Will multiple events conflict when running at the same time? No, they are executed sequentially, but complex operations are recommended for concurrent testing.
Basically that's it. Although the event scheduler function is not complicated, it is easy to ignore its details, such as time setting, execution frequency, whether it is enabled, etc. As long as you understand these places, daily maintenance tasks can save a lot of trouble.
The above is the detailed content of mysql event scheduler example. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
