MySQL :: MySQL 8.0 Reference Manual

Search Results

Displaying 671 to 680 of 949 total results

https://dev.mysql.com/doc/refman/8.0/en/create-database.html

An error occurs if the database exists and you did not specify IF NOT EXISTS. For information about character set and collation names, see Chapter 12, Character Sets, Collations, Unicode. If a database name contains special characters, the name for ... CREATE {DATABASE | SCHEMA} [IF NOT EXISTS] db_name [create_option] ...

15.1.20.2 CREATE TEMPORARY TABLE Statement

https://dev.mysql.com/doc/refman/8.0/en/create-temporary-table.html

When innodb_strict_mode is enabled (the default), CREATE TEMPORARY TABLE returns an error if ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE is specified. You can use the TEMPORARY keyword when creating a table. A TEMPORARY table is visible only within the ...

15.1.22 CREATE TRIGGER Statement

https://dev.mysql.com/doc/refman/8.0/en/create-trigger.html

IF NOT EXISTS prevents an error from occurring if a trigger having the same name, on the same table, exists in the same schema. CREATE [DEFINER = user] TRIGGER [IF NOT EXISTS] trigger_name trigger_time trigger_event ON tbl_name FOR EACH ROW ...

8.2.8 Adding Accounts, Assigning Privileges, and Dropping Accounts

https://dev.mysql.com/doc/refman/8.0/en/creating-accounts.html

For any operation that modifies a grant table, the server checks whether the table has the expected structure and produces an error if not. To manage MySQL accounts, use the SQL statements intended for that purpose: CREATE USER and DROP USER create ...

16.7 Data Dictionary Usage Differences

https://dev.mysql.com/doc/refman/8.0/en/data-dictionary-usage-differences.html

Use of a data dictionary-enabled MySQL server entails some operational differences compared to a server that does not have a data dictionary: Previously, enabling the innodb_read_only system variable prevented creating and dropping tables only for ...

13.2 Date and Time Data Types

https://dev.mysql.com/doc/refman/8.0/en/date-and-time-types.html

For temporal types that include a date part (DATE, DATETIME, and TIMESTAMP), use of these values may produce warning or errors. The date and time data types for representing temporal values are DATE, TIME, DATETIME, TIMESTAMP, and YEAR. Each ...

13.2.2 The DATE, DATETIME, and TIMESTAMP Types

https://dev.mysql.com/doc/refman/8.0/en/datetime.html

This section describes their characteristics, how they are similar, and how they differ. MySQL recognizes DATE, DATETIME, and TIMESTAMP values in several formats, described in Section 11.1.3, “Date and Time Literals”. For the DATE and DATETIME ...

7.6.5.1 Installing or Uninstalling ddl_rewriter

https://dev.mysql.com/doc/refman/8.0/en/ddl-rewriter-installation.html

If the plugin fails to initialize, check the server error log for diagnostic messages. This section describes how to install or uninstall the ddl_rewriter plugin. For general information about installing plugins, see Section 7.6.1, “Installing ...

15.5.3 DEALLOCATE PREPARE Statement

https://dev.mysql.com/doc/refman/8.0/en/deallocate-prepare.html

Attempting to execute a prepared statement after deallocating it results in an error. {DEALLOCATE | DROP} PREPARE stmt_name To deallocate a prepared statement produced with PREPARE, use a DEALLOCATE PREPARE statement that refers to the prepared ...

10.2.5.3 Optimizing DELETE Statements

https://dev.mysql.com/doc/refman/8.0/en/delete-optimization.html

Truncate operations are not transaction-safe; an error occurs when attempting one in the course of an active transaction or active table lock. The time required to delete individual rows in a MyISAM table is exactly proportional to the number of ...

Displaying 671 to 680 of 949 total results