Extracting years in MySQL can use the YEAR() function, 1. Use YEAR(date_column) to extract years from DATE, DATETIME or TIMESTAMP type fields; 2. It is often used to count annual data volume, group by year, or filter specific year records; 3. Use WHERE YEAR(date_column) when querying. The data can be filtered, but may affect index performance; 4. It is recommended to replace it with range query to improve efficiency, such as WHERE date_column >= 'YYYY-01-01' AND date_column
Extracting years from dates in MySQL is a very common requirement, such as if you want to count the total amount of data for a certain year, or filter out records for a certain year. There is no need for complicated operations at this time, you can do it with a built-in function.

Extract year using YEAR()
function
MySQL provides the YEAR()
function that extracts years directly from fields of date or datetime type. It is very simple to use:
SELECT YEAR(order_date) AS order_year FROM orders;
The above example extracts the year from the order_date
field of orders
table. This function is suitable for fields of type DATE
, DATETIME
, and TIMESTAMP
.

Common scenarios include:
- Statistics of the order quantity per year
- Display data trends by grouping
- Query data for a specific year (such as
WHERE YEAR(create_time) = 2023
)
Use year filtering in query conditions
If you want to find data for a certain year, you can use the YEAR()
function in WHERE
condition:

SELECT * FROM sales WHERE YEAR(sale_date) = 2022;
This allows you to filter out all sales records for 2022. But it should be noted that this writing method may not be able to effectively utilize indexes, especially when the table data is large, it will affect query performance.
If you often need to query by year, it is recommended:
- Add a separate year field and index it
- Or use a scope query instead of
YEAR()
, for example:
SELECT * FROM sales WHERE sale_date >= '2022-01-01' AND sale_date < '2023-01-01';
This approach is usually more efficient because the database can use indexes on sale_date
.
Combined with GROUP BY
Group Statistics by Year
When doing data summary, it is often necessary to group statistics by year. For example, counting annual sales:
SELECT YEAR(order_date) AS order_year, SUM(amount) AS total_amount FROM orders GROUP BY YEAR(order_date);
This will result in the total amount for each year. If you want to further refine to a month or quarter, you can also extract the month or quarter fields to group them together.
Need to note:
- If the data for a certain year is empty, the result will not show that year.
- You can cooperate with
ORDER BY
to make the results sorted by year more intuitive
Basically that's it. Using YEAR()
is the most direct way, but performance issues must be considered in large amounts of data. The writing method may be better if you use it in another way.
The above is the detailed content of mysql get year from date. 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

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;
