mysql学习记录(十一)--事件调度器_MySQL
一、理论:
1.优势:
1)减少系统管理员的操作风险,有利于数据库整体迁移。因数据库迁移时即可同时迁移调度事件
2.场景:
1)定期收集统计信息
2)清理历史数据
3)数据库检查
3.要点:
1)在性能要求高且重要的数据库中要慎重部署和启用调度器
2)过于复杂的更适合用程序
3)开启和关闭事件调度器需要具有超级用户权限
二、实践:
mysql> use test1; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> create table test(id1 varchar(10),create_time datetime); Query OK, 0 rows affected (0.02 sec) mysql> create event test_event_1 -> on schedule -> every 5 second -> do -> insert into test1.test(id1,create_time) -> values ('test',now()); Query OK, 0 rows affected (0.01 sec) mysql> show events \G; *************************** 1. row *************************** Db: test1 Name: test_event_1 Definer: root@localhost Time zone: SYSTEM Type: RECURRING Execute at: NULL Interval value: 5 Interval field: SECOND Starts: 2015-10-14 06:33:17 Ends: NULL Status: ENABLED Originator: 1 character_set_client: utf8 collation_connection: utf8_general_ci Database Collation: utf8_general_ci 1 row in set (0.01 sec) ERROR: No query specified mysql> select * from test; Empty set (0.00 sec) mysql> show variables like '%scheduler%'; +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | event_scheduler | OFF | +-----------------+-------+ 1 row in set (0.00 sec) mysql> set global event_scheduler = 1 ; Query OK, 0 rows affected (0.00 sec) mysql> show variables like '%scheduler%'; +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | event_scheduler | ON | +-----------------+-------+ 1 row in set (0.00 sec) mysql> show processlist \G; *************************** 1. row *************************** Id: 17 User: root Host: localhost db: test1 Command: Sleep Time: 247901 State: Info: NULL *************************** 2. row *************************** Id: 21 User: root Host: localhost db: test1 Command: Query Time: 0 State: NULL Info: show processlist *************************** 3. row *************************** Id: 22 User: event_scheduler Host: localhost db: NULL Command: Daemon Time: 1 State: Waiting for next activation Info: NULL 3 rows in set (0.00 sec) ERROR: No query specified mysql> select * from test; +------+---------------------+ | id1 | create_time | +------+---------------------+ | test | 2015-10-14 06:33:57 | | test | 2015-10-14 06:34:02 | | test | 2015-10-14 06:34:07 | | test | 2015-10-14 06:34:12 | | test | 2015-10-14 06:34:17 | | test | 2015-10-14 06:34:22 | +------+---------------------+ 6 rows in set (0.00 sec) mysql> create event trunc_test -> on schedule every 1 minute -> do truncate table test; Query OK, 0 rows affected (0.00 sec) mysql> select * from test; +------+---------------------+ | id1 | create_time | +------+---------------------+ | test | 2015-10-14 06:34:52 | | test | 2015-10-14 06:34:57 | | test | 2015-10-14 06:35:02 | | test | 2015-10-14 06:35:07 | | test | 2015-10-14 06:35:12 | | test | 2015-10-14 06:35:17 | | test | 2015-10-14 06:35:22 | | test | 2015-10-14 06:35:27 | | test | 2015-10-14 06:35:32 | | test | 2015-10-14 06:35:37 | +------+---------------------+ 10 rows in set (0.00 sec) mysql> select * from test; +------+---------------------+ | id1 | create_time | +------+---------------------+ | test | 2015-10-14 06:37:52 | | test | 2015-10-14 06:37:57 | +------+---------------------+ 2 rows in set (0.00 sec) mysql> show processlist \G; *************************** 1. row *************************** Id: 17 User: root Host: localhost db: test1 Command: Sleep Time: 248177 State: Info: NULL *************************** 2. row *************************** Id: 21 User: root Host: localhost db: test1 Command: Query Time: 0 State: NULL Info: show processlist *************************** 3. row *************************** Id: 22 User: event_scheduler Host: localhost db: NULL Command: Daemon Time: 2 State: Waiting for next activation Info: NULL 3 rows in set (0.00 sec) ERROR: No query specified mysql> alter event trunc_test disable; Query OK, 0 rows affected (0.02 sec) mysql> select * from test; +------+---------------------+ | id1 | create_time | +------+---------------------+ | test | 2015-10-14 06:38:52 | | test | 2015-10-14 06:38:57 | | test | 2015-10-14 06:39:02 | | test | 2015-10-14 06:39:07 | | test | 2015-10-14 06:39:12 | | test | 2015-10-14 06:39:17 | | test | 2015-10-14 06:39:22 | | test | 2015-10-14 06:39:27 | | test | 2015-10-14 06:39:32 | | test | 2015-10-14 06:39:37 | +------+---------------------+ 10 rows in set (0.00 sec) mysql> select * from test; +------+---------------------+ | id1 | create_time | +------+---------------------+ | test | 2015-10-14 06:38:52 | | test | 2015-10-14 06:38:57 | | test | 2015-10-14 06:39:02 | | test | 2015-10-14 06:39:07 | | test | 2015-10-14 06:39:12 | | test | 2015-10-14 06:39:17 | | test | 2015-10-14 06:39:22 | | test | 2015-10-14 06:39:27 | | test | 2015-10-14 06:39:32 | | test | 2015-10-14 06:39:37 | | test | 2015-10-14 06:39:42 | | test | 2015-10-14 06:39:47 | | test | 2015-10-14 06:39:52 | | test | 2015-10-14 06:39:57 | | test | 2015-10-14 06:40:02 | | test | 2015-10-14 06:40:07 | +------+---------------------+ 16 rows in set (0.00 sec) mysql> alter event test_event_1 disable; Query OK, 0 rows affected (0.00 sec) mysql> select * from test; +------+---------------------+ | id1 | create_time | +------+---------------------+ | test | 2015-10-14 06:38:52 | | test | 2015-10-14 06:38:57 | | test | 2015-10-14 06:39:02 | | test | 2015-10-14 06:39:07 | | test | 2015-10-14 06:39:12 | | test | 2015-10-14 06:39:17 | | test | 2015-10-14 06:39:22 | | test | 2015-10-14 06:39:27 | | test | 2015-10-14 06:39:32 | | test | 2015-10-14 06:39:37 | | test | 2015-10-14 06:39:42 | | test | 2015-10-14 06:39:47 | | test | 2015-10-14 06:39:52 | | test | 2015-10-14 06:39:57 | | test | 2015-10-14 06:40:02 | | test | 2015-10-14 06:40:07 | | test | 2015-10-14 06:40:12 | | test | 2015-10-14 06:40:17 | | test | 2015-10-14 06:40:22 | | test | 2015-10-14 06:40:27 | +------+---------------------+ 20 rows in set (0.00 sec) mysql> drop event test_event_1; Query OK, 0 rows affected (0.01 sec) mysql> show events \G; *************************** 1. row *************************** Db: test1 Name: trunc_test Definer: root@localhost Time zone: SYSTEM Type: RECURRING Execute at: NULL Interval value: 1 Interval field: MINUTE Starts: 2015-10-14 06:34:48 Ends: NULL Status: DISABLED Originator: 1 character_set_client: utf8 collation_connection: utf8_general_ci Database Collation: utf8_general_ci 1 row in set (0.00 sec) ERROR: No query specified

Hot AI Tools

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

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

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

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


![Event ID 4660: Object deleted [Fix]](https://img.php.cn/upload/article/000/887/227/168834320512143.png?x-oss-process=image/resize,m_fill,h_207,w_330)
Some of our readers encountered event ID4660. They're often not sure what to do, so we explain it in this guide. Event ID 4660 is usually logged when an object is deleted, so we will also explore some practical ways to fix it on your computer. What is event ID4660? Event ID 4660 is related to objects in Active Directory and will be triggered by any of the following factors: Object Deletion – A security event with Event ID 4660 is logged whenever an object is deleted from Active Directory. Manual changes – Event ID 4660 may be generated when a user or administrator manually changes the permissions of an object. This can happen when changing permission settings, modifying access levels, or adding or removing people or groups

On iPhones running iOS 16 or later, you can display upcoming calendar events directly on the lock screen. Read on to find out how it's done. Thanks to watch face complications, many Apple Watch users are used to being able to glance at their wrist to see the next upcoming calendar event. With the advent of iOS16 and lock screen widgets, you can view the same calendar event information directly on your iPhone without even unlocking the device. The Calendar Lock Screen widget comes in two flavors, allowing you to track the time of the next upcoming event, or use a larger widget that displays event names and their times. To start adding widgets, unlock your iPhone using Face ID or Touch ID, press and hold

When a value is added to the input box, the oninput event occurs. You can try running the following code to understand how to implement oninput events in JavaScript - Example<!DOCTYPEhtml><html> <body> <p>Writebelow:</p> <inputtype="text"

How to implement calendar functions and event reminders in PHP projects? Calendar functionality and event reminders are one of the common requirements when developing web applications. Whether it is personal schedule management, team collaboration, or online event scheduling, the calendar function can provide convenient time management and transaction arrangement. Implementing calendar functions and event reminders in PHP projects can be completed through the following steps. Database design First, you need to design a database table to store information about calendar events. A simple design could contain the following fields: id: unique to the event

jQuery is a popular JavaScript library that can be used to simplify DOM manipulation, event handling, animation effects, etc. In web development, we often encounter situations where we need to change event binding on select elements. This article will introduce how to use jQuery to bind select element change events, and provide specific code examples. First, we need to create a dropdown menu with options using labels:

Commonly used events in jquery are: 1. Window events; 2. Mouse events, which are events generated when the user moves or clicks the mouse on the document, including mouse clicks, move-in events, move-out events, etc.; 3. Keyboard events, Events are generated every time the user presses or releases a key on the keyboard, including key press events, key release events, etc.; 4. Form events, such as the focus() event will be triggered when an element gains focus, and the focus() event will be triggered when it loses focus. The blur() event is triggered, and the submit() event is triggered when the form is submitted.

Methods for building event-based applications in PHP include using the EventSourceAPI to create an event source and using the EventSource object to listen for events on the client side. Send events using Server Sent Events (SSE) and listen for events on the client side using an XMLHttpRequest object. A practical example is to use EventSource to update inventory counts in real time in an e-commerce website. This is achieved on the server side by randomly changing the inventory and sending updates, and the client listens for inventory updates through EventSource and displays them in real time.

Vue.js is a lightweight JavaScript framework that is easy to use, efficient and flexible. It is one of the most popular front-end frameworks currently. In Vue.js, input box binding events are a very common requirement. This article will introduce the input box binding events in the Vue document in detail. 1. Basic concepts In Vue.js, the input box binding event refers to binding the value of the input box to the data object of the Vue instance, thereby achieving two-way binding of input and response. In Vue.j
