Using cursor data
After a cursor is opened, you can use the FETCH statement to access each of its rows separately. FETCH specifies what data (required columns) to retrieve and where the retrieved data is stored. It also moves the internal row pointer in the cursor forward so that the next FETCH statement retrieves the next row (without reading the same row repeatedly).
The first example retrieves a single row (the first row) from the cursor:
Input:
create procedure processorders() BEGIN -- declare local variables declare o int; -- declare the cursor declare ordernumbers cursor for select order_num from orders: -- open the cursor open ordernumbers; -- get order number fetch ordernumbers into o; -- close the cursor close ordernumbers; end;
Analysis: where FETCH is used to retrieve the order_num column of the current row ( will automatically start from the first line) into a locally declared variable named o. No processing is performed on the retrieved data.
In the next example, loop to retrieve the data, from the first row to the last row:
Input:
create procedure processorders() BEGIN -- declare local variables declare done boolean default 0; declare o int; -- declare the cursor declare ordernumbers cursor for select order_num from orders: --declare continue handler declare continue handler for sqlstate '02000' set done = 1; -- open the cursor open ordernumbers; --loop through all rows repeat -- get order number fetch ordernumbers into o; -- end of loop until done end repeat; -- close the cursor close ordernumbers; end;
Analysis: Like the previous example, this example uses FETCH Retrieve the current order_num into the declared variable named o. But unlike the previous example, the FETCH in this example is inside a REPEAT, so it is executed repeatedly until done is true (as specified by UNTILdone END REPEAT;). To make this work, define the variable done with a DEFAULT 0 (false, not finished). So, how can done be set to true at the end? The answer is to use the following statement:
declare continue handler for sqlstate '02000' set done = 1;
This statement defines a CONTINUE HANDLER, which is code that is executed when the condition occurs. Here, it states that when SQLSTATE '02000' occurs, SET done=1. SQLSTATE '02000' is a not found condition that occurs when REPEAT cannot continue because there are no more rows for the loop to loop through.
MySQL error codes For a list of MySQL error codes used by MySQL 5, see http://dev.mysql.com/doc/mysql/en/error-handling.html.
Order of DECLARE statements There is a specific order in which DECLARE statements are issued. Local variables defined with the DECLARE statement must be defined before any cursor or handle is defined, and handles must be defined after the cursor. Failure to observe this order will produce an error message.
If this stored procedure is called, it will define several variables and a CONTINUE HANDLER, define and open a cursor, repeatedly read all rows, and then close the cursor. If everything is fine, you can put any necessary processing inside the loop (after the FETCH statement, but before the loop ends).
Repeat or loop? In addition to the REPEAT statement used here, MySQL also supports loop statements, which can be used to repeatedly execute code until manually exited using the LEAVE statement. Usually the syntax of the REPEAT statement makes it more suitable for looping on cursors.
To organize this, here is a further modified version of our cursor stored procedure example, this time doing some actual processing of the retrieved data: Input:create procedure processorders() BEGIN -- declare local variables declare done boolean default 0; declare o int; declare t decimal(8,2); -- declare the cursor declare ordernumbers cursor for select order_num from orders; -- declare continue handler declare continue handler for sqlstate '02000' set done = 1; -- create a table to store the results create table if not exists ordertotals (order_num int, total decimal(8,2)); -- open the cursor open ordernumbers; -- loop through all rows repeat -- get order number fetch ordernumbers into o; -- get the total for this order call ordertotal(o,1,t); -- insert order and total into ordertotals insert into ordertotals(order_num,total) values(o,t); -- end of loop until done end repeat; -- close the cursor close ordernumbers; END;Analysis: In this example, we added another variable named t (to store the total of each order). This stored procedure also creates a new table on the fly (if it does not already exist) named ordertotals . This table will hold the results generated by the stored procedure. FETCH takes each order_num as before, then uses CALL to execute another stored procedure (which we created in the previous chapter) to calculate the taxed total for each order (the result is stored in t ). Finally, use INSERT to save the order number and total for each order. This stored procedure does not return data, but it is able to create and populate another table, which can be viewed with a simple SELECT statement: Input:
select * from ordertotals;Output :
The above is the detailed content of MySQL using cursor data example tutorial. For more information, please follow other related articles on the PHP Chinese website!

Stored procedures are precompiled SQL statements in MySQL for improving performance and simplifying complex operations. 1. Improve performance: After the first compilation, subsequent calls do not need to be recompiled. 2. Improve security: Restrict data table access through permission control. 3. Simplify complex operations: combine multiple SQL statements to simplify application layer logic.

The working principle of MySQL query cache is to store the results of SELECT query, and when the same query is executed again, the cached results are directly returned. 1) Query cache improves database reading performance and finds cached results through hash values. 2) Simple configuration, set query_cache_type and query_cache_size in MySQL configuration file. 3) Use the SQL_NO_CACHE keyword to disable the cache of specific queries. 4) In high-frequency update environments, query cache may cause performance bottlenecks and needs to be optimized for use through monitoring and adjustment of parameters.

The reasons why MySQL is widely used in various projects include: 1. High performance and scalability, supporting multiple storage engines; 2. Easy to use and maintain, simple configuration and rich tools; 3. Rich ecosystem, attracting a large number of community and third-party tool support; 4. Cross-platform support, suitable for multiple operating systems.

The steps for upgrading MySQL database include: 1. Backup the database, 2. Stop the current MySQL service, 3. Install the new version of MySQL, 4. Start the new version of MySQL service, 5. Recover the database. Compatibility issues are required during the upgrade process, and advanced tools such as PerconaToolkit can be used for testing and optimization.

MySQL backup policies include logical backup, physical backup, incremental backup, replication-based backup, and cloud backup. 1. Logical backup uses mysqldump to export database structure and data, which is suitable for small databases and version migrations. 2. Physical backups are fast and comprehensive by copying data files, but require database consistency. 3. Incremental backup uses binary logging to record changes, which is suitable for large databases. 4. Replication-based backup reduces the impact on the production system by backing up from the server. 5. Cloud backups such as AmazonRDS provide automation solutions, but costs and control need to be considered. When selecting a policy, database size, downtime tolerance, recovery time, and recovery point goals should be considered.

MySQLclusteringenhancesdatabaserobustnessandscalabilitybydistributingdataacrossmultiplenodes.ItusestheNDBenginefordatareplicationandfaulttolerance,ensuringhighavailability.Setupinvolvesconfiguringmanagement,data,andSQLnodes,withcarefulmonitoringandpe

Optimizing database schema design in MySQL can improve performance through the following steps: 1. Index optimization: Create indexes on common query columns, balancing the overhead of query and inserting updates. 2. Table structure optimization: Reduce data redundancy through normalization or anti-normalization and improve access efficiency. 3. Data type selection: Use appropriate data types, such as INT instead of VARCHAR, to reduce storage space. 4. Partitioning and sub-table: For large data volumes, use partitioning and sub-table to disperse data to improve query and maintenance efficiency.

TooptimizeMySQLperformance,followthesesteps:1)Implementproperindexingtospeedupqueries,2)UseEXPLAINtoanalyzeandoptimizequeryperformance,3)Adjustserverconfigurationsettingslikeinnodb_buffer_pool_sizeandmax_connections,4)Usepartitioningforlargetablestoi


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

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

Hot Article

Hot Tools

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

SublimeText3 Linux new version
SublimeText3 Linux latest version

Dreamweaver Mac version
Visual web development tools

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

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