In MySQL there’s a system variable called sql_quote_show_create which is used to determine whether or not to use quoted identifiers when using the SHOW CREATE TABLE and SHOW CREATE DATABASE statements.
By default sql_quote_show_create is set to 1, which means that quotes/backticks will be generated whenever these statements are run, but we can also change this value to 0 in order to disable quotes.
Below are examples of checking this variable and setting it.
Continue readingIf you’re getting an error that reads “Failed to generate invisible primary key. Column ‘my_row_id’ already exists“, it’s probably because you’re trying to create a table without a primary key, and you’ve named a column my_row_id.
When your system has generated invisible primary keys (GIPKs) enabled, and you create an InnoDB table without explicitly defining a primary key, MySQL automatically creates an invisible column called my_row_id and creates a primary key constraint against it. This is called a generated invisible primary key.
However, if you name one of your columns my_row_id, then MySQL can’t create the GIPK due to the column already existing.
There are several ways to go about fixing this issue.
Continue readingWhile primary keys are generally considered a necessity when it comes to relational databases, they’re usually included in the SQL code that creates the database table.
MySQL 8.0.30 introduced generated invisible primary keys which provide an alternative to explicitly specifying a primary key for a table.
A generated invisible primary key (GIPK) is a primary key that’s created implicitly by the MySQL server. If we create a table without an explicit primary key, the MySQL server automatically creates a generated invisible primary key for us (assuming it’s an InnoDB table and that GIPKs are enabled).
Continue readingMySQL allows us to easily add a primary key constraint to an existing column. We can use the ALTER TABLE statement to achieve this outcome.
We can also use the ADD PRIMARY KEY clause, which can be useful for adding composite primary keys.
MySQL supports invisible columns (from MySQL 8.0.23), which means we can control whether a column is considered visible or invisible.
Invisible columns are hidden from queries that use the asterisk wildcard (*) in their SELECT list, but can be selected by explicitly naming the column.
We can create invisible columns when creating a table. We can also add invisible columns to existing tables. And we can modify existing columns to be invisible (and vice-versa).
Continue readingMySQL has a SHOW CREATE DATABASE statement that shows the CREATE DATABASE statement that would be used to recreate the database.
We can use the SHOW CREATE DATABASE statement to create an identical database on another server, or to create a similar database on the same server (while changing the name).
We can alternatively use SHOW CREATE SCHEMA to do the same thing (SHOW CREATE SCHEMA is a synonym for SHOW CREATE DATABASE).
Primary keys are a crucial part of relational database management systems (RDBMSs). Most of the time we create a primary key constraint against a single column that is the unique identifier for the table.
But we can also create primary key constraints against more than one column. When we do this, we call it a composite primary key.
Composite keys can be handy when we don’t have a single column that contains unique values, but multiple columns can be combined to create a unique value.
Continue readingIf you’re using the REPLACE statement to replace rows in MySQL, but it’s inserting duplicate rows instead, it could be due to one of the following reasons.
In MySQL, we can use the SHOW CREATE TABLE statement to produce a CREATE TABLE statement from an existing table.
This enables us to generate a script that we can use to recreate the table on another database, or on the same database at a later date. Or we could use it to create another similar table. We would need to modify the code accordingly when doing this, but it could give us a good starting point.
We can also use SHOW CREATE TABLE for a quick way to take a look at the table’s structure, and check for things like data types, primary keys, foreign keys, etc.
If you’re getting an error that reads something like “Multiple primary key defined” in MySQL, it’s probably because you’re defining more than one primary key to a table.
A table can only have one primary key in MySQL.
It’s possible that you were trying to create a composite primary key (i.e. a primary key consisting of multiple columns), in which case, you can fix the issue with a simple modification to your code.
Otherwise, you will need to decide which column should be the primary key for the table and only apply the PRIMARY KEY definition to that column.