Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Databases and Redis

A query fails with No database selected

ErrorERROR 1046 (3D000): No database selected

Short answer

Error 1046 means the connection has no default database and the statement used a bare table name. Choose one with USE db_name, start the client with a database name, or write db_name.table_name in the query.

  • Applies to MySQL 8.4, mysql client
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Ask the server which database the current session uses. NULL means none is selected.

    SELECT DATABASE();
  2. 2Match what you see, then jump to its fix

    1. 1SELECT DATABASE() returns NULL right after connectingThe session never chose a databaseFix
    2. 2The error appears on the first CREATE TABLE or INSERT of a dump or migration fileAn SQL file is loaded without a databaseFix
    3. 3The same command works on one machine or user and fails on anotherThe default database is set in a config file that is not readFix

What does the error look like?

  • ERROR 1046 (3D000): No database selected

Cause 1 of 3

The session never chose a database

1Check

List what exists, then pick the one you need.

SHOW DATABASES;

2Fix

Select it inside the client, or name it when you start the client.

USE shop;

# or at start-up
mysql -u appuser -p shop

3Verify

DATABASE() now returns the name.

SELECT DATABASE();

Confirmed by dev.mysql.com

Did this fix it?

Cause 2 of 3

An SQL file is loaded without a database

1Check

Check whether the file starts with USE or CREATE DATABASE, and how you run it.

head -n 20 schema.sql

2Fix

Name the database on the command line; this is the same as putting USE at the top of the input.

mysql -u appuser -p shop < schema.sql

3Verify

The import finishes with no 1046 error and the tables exist.

mysql -u appuser -p shop -e 'SHOW TABLES;'

Confirmed by dev.mysql.com

Did this fix it?

Cause 3 of 3

The default database is set in a config file that is not read

1Check

The database option is meant for option files. Confirm the file and group the client reads.

mysql --print-defaults

2Fix

Add a database line to the [client] or [mysql] group of the option file you actually use, or pass it on the command line.

[mysql]
database=shop

3Verify

Start the client with no database argument and check DATABASE().

mysql -u appuser -p -e 'SELECT DATABASE();'

Confirmed by dev.mysql.com

Did this fix it?

How do I stop it coming back?

  • Start every script with an explicit USE or pass the database name to the client.
  • Use the db_name.table_name form in one-off queries from tools that open a fresh connection.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.