The key to MySQL date format is to distinguish the storage type and display format. 1. DATE displays YYYY-MM-DD by default, DATETIME displays YYYY-MM-DD HH:MM:SS; 2. Use the DATE_FORMAT function to customize the format, such as %Y year %m month %d day; 3. Choose different formats in different scenarios, such as %Y year %m month %d day for user displays, and logs use %Y-%m-%d %H:%i:%s; 4. Note that TIMESTAMP automatically handles time zone conversion, while DATETIME saves data as it is. Mastering these key points can deal with common date format problems.
MySQL's date format is actually not that complicated, but it is easy to get confused when used. The key is to distinguish the difference between the stored date type and the display format . Simply put, you can save dates as DATE, DATETIME or TIMESTAMP types, but if you want to display them, you need to use formatting functions.

Default display formats for DATE and DATETIME
In MySQL, the DATE type appears by default as YYYY-MM-DD
, while DATETIME is YYYY-MM-DD HH:MM:SS
.
For example, you have a user table with the registration time field:
SELECT register_time FROM users;
If register_time
is of type DATETIME, the default output is the complete timestamp, like 2024-10-05 14:30:00
. Although this format is standard, it sometimes does not meet business needs. For example, if you want to display it as "October 5, 2024" or only take the year and month.

Use the DATE_FORMAT function to customize the format
If you need to display dates in your own way, you need to use DATE_FORMAT(date, format)
function. Its core is format string, and commonly used format characters include:
-
%Y
: Four-digit year (such as 2024) -
%y
: a double-digit year (such as 24) -
%m
: Double-digit month (01 to 12) -
%c
: Digital months (1 to 12, no zero compensation) -
%d
: Date of double digits (01 to 31) -
%H
: 24-hour hours -
%h
: 12-hour hours -
%i
: minutes -
%s
: seconds
For example:

SELECT DATE_FORMAT(register_time, '%Y year %m month %d day') AS formatted_date FROM users;
The result will be 2024年10月05日
, which looks more friendly.
Common format suggestions for different scenarios
Depending on the purpose, you can choose different formats:
- Show to the user:
%Y年%m月%d日
or%Y-%m-%d
- Log or interface returns:
%Y-%m-%d %H:%i:%s
- As long as year and month:
%Y-%m
- The time you are used to in Chinese: you can use
CONCAT(DATE_FORMAT(...), IF(HOUR(...) < 12, ' 上午', ' 下午'))
For example, if you want to display "October 2024" in the report, you can write it like this:
SELECT DATE_FORMAT(register_time, '%Y year %m month') AS report_month FROM users;
Pay attention to the difference between time zone and data type
Another point that is easy to ignore is: TIMESTAMP and DATETIME are different when dealing with time zones .
For example, if you insert a time in the East Eighth District:
INSERT INTO users (register_time) VALUES ('2024-10-05 10:00:00');
If the field is TIMESTAMP, it will be automatically converted to UTC storage; it will be turned back according to the current connection time zone during query. And DATETIME is saved as it is and will not touch your data.
So when you find that the format is correct but the time difference is several hours, it is likely that it is not a problem with the format, but a time zone is wrong.
Basically that's it. By using DATE_FORMAT well and understanding behaviors of different date types, you can cope with most MySQL date format usage scenarios.
The above is the detailed content of mysql date format. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

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

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

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The default user name of MySQL is usually 'root', but the password varies according to the installation environment; in some Linux distributions, the root account may be authenticated by auth_socket plug-in and cannot log in with the password; when installing tools such as XAMPP or WAMP under Windows, root users usually have no password or use common passwords such as root, mysql, etc.; if you forget the password, you can reset it by stopping the MySQL service, starting in --skip-grant-tables mode, updating the mysql.user table to set a new password and restarting the service; note that the MySQL8.0 version requires additional authentication plug-ins.

GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.

There are three ways to modify or reset MySQLroot user password: 1. Use the ALTERUSER command to modify existing passwords, and execute the corresponding statement after logging in; 2. If you forget your password, you need to stop the service and start it in --skip-grant-tables mode before modifying; 3. The mysqladmin command can be used to modify it directly by modifying it. Each method is suitable for different scenarios and the operation sequence must not be messed up. After the modification is completed, verification must be made and permission protection must be paid attention to.

MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to

The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands

InnoDB implements repeatable reads through MVCC and gap lock. MVCC realizes consistent reading through snapshots, and the transaction query results remain unchanged after multiple transactions; gap lock prevents other transactions from inserting data and avoids phantom reading. For example, transaction A first query gets a value of 100, transaction B is modified to 200 and submitted, A is still 100 in query again; and when performing scope query, gap lock prevents other transactions from inserting records. In addition, non-unique index scans may add gap locks by default, and primary key or unique index equivalent queries may not be added, and gap locks can be cancelled by reducing isolation levels or explicit lock control.

Toalteralargeproductiontablewithoutlonglocks,useonlineDDLtechniques.1)IdentifyifyourALTERoperationisfast(e.g.,adding/droppingcolumns,modifyingNULL/NOTNULL)orslow(e.g.,changingdatatypes,reorderingcolumns,addingindexesonlargedata).2)Usedatabase-specifi

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation
