PDF (US Ltr) - 37.9Mb PDF (A4) - 38.0Mb PDF (RPM) - 37.3Mb HTML Download (TGZ) - 10.3Mb HTML Download (Zip) - 10.3Mb HTML Download (RPM) - 8.9Mb Man Pages (TGZ) - 216.7Kb Man Pages (Zip) - 329.5Kb Info (Gzip) - 3.4Mb Info (Zip) - 3.4Mb My SQL Backup and Recovery My SQL Globalization My SQL Information Schema My SQL Installation Guide My SQL and Linux/Unix My SQL and OS X My SQL Partitioning My SQL Performance Schema My SQL Replication Using the My SQL Yum Repository My SQL Restrictions and Limitations Security in My SQL My SQL and Solaris Building My SQL from Source Starting and Stopping My SQL My SQL Tutorial My SQL and Windows My SQL NDB Cluster 7.5 option as part of a table reference.This option takes a list of one or more partitions or subpartitions (or both).Use OPEN, FETCH, and CLOSE in the execution or exception sections of your programs.To use an explicit cursor, you must first declare it in the declaration section of a block or package. This was the first surprise: I couldn't find text in the documentation telling about this behaviour. Fetching a row does lock the row, as can be seen in the output.Dynamic cursors are implemented with the EXECUTE IMMEDIATE statement.
Static cursors are used only for DML statements (SELECT, INSERT, UPDATE, DELETE, MERGE, or SELECT FOR UPDATE).Only the partitions (or subpartitions) listed are checked for matches, and a row that is not in any of these partitions or subpartitions is not updated, whether it satisfies the clause, are flagged as unsafe for statement-based replication.(This is because the order in which the rows are updated determines which rows are ignored.) With this change, such statements produce a warning in the log when using statement-based mode and are logged using the row-based format when using mode.For multiple-table updates, there is no guarantee that assignments are carried out in any particular order.If you set a column to the value it currently has, My SQL notices this and does not update it.