Why Does MySQL Allow Non-Grouped Columns in GROUP BY Queries?
MySQL's Non-Standard GROUP BY Extension: Allowing Non-Grouped Column Selection
The standard SQL syntax prohibits selecting non-aggregate fields that are not explicitly grouped in the GROUP BY clause of an aggregate query. However, MySQL deviates from this standard by allowing such selections.
Standard SQL vs. MySQL's Extension
Until 1992, the standard SQL specification prohibited this behavior, ensuring that aggregate queries only returned aggregated values or columns grouped in the GROUP BY clause.
However, with the release of SQL-2003, the standard was amended to allow the selection of columns that are functionally dependent on the grouping columns. MySQL's extension, however, goes beyond this standard by permitting all columns to be selected, regardless of their functional dependencies.
Implications of MySQL's Extension
This extension has several implications:
- Performance Improvement: Avoiding unnecessary column sorting and grouping can significantly improve query performance.
- Maintainability: Allowing non-grouped column selection simplifies the writing and maintenance of complex queries.
- Indeterminate Results: However, this extension introduces a potential for indeterminate results if the non-grouped columns contain different values within each group.
MySQL's Motivation for the Extension
MySQL implemented this extension to comply with SQL-2003 standards, while also addressing the performance and maintainability concerns mentioned above. However, they chose a simplified approach by allowing all columns to be selected, rather than implementing a more complex mechanism to identify functionally dependent columns.
Disabling the Extension
If desired, users can disable the extension by setting the sql_mode to ONLY_FULL_GROUP_BY. This will restore the stricter SQL-92 behavior, ensuring that non-grouped columns cannot be selected in aggregate queries.
Recent Developments
In 2011, PostgreSQL added a more restrictive implementation of this feature, closer to the SQL standard. MySQL's handling of GROUP BY was further improved in version 5.7 (2015), incorporating a mechanism to recognize functional dependencies, aligning it more closely with the standard.
The above is the detailed content of Why Does MySQL Allow Non-Grouped Columns in GROUP BY Queries?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

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

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

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

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 article discusses using MySQL's ALTER TABLE statement to modify tables, including adding/dropping columns, renaming tables/columns, and changing column data types.

Article discusses configuring SSL/TLS encryption for MySQL, including certificate generation and verification. Main issue is using self-signed certificates' security implications.[Character count: 159]

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The article discusses dropping tables in MySQL using the DROP TABLE statement, emphasizing precautions and risks. It highlights that the action is irreversible without backups, detailing recovery methods and potential production environment hazards.

Article discusses using foreign keys to represent relationships in databases, focusing on best practices, data integrity, and common pitfalls to avoid.

The article discusses creating indexes on JSON columns in various databases like PostgreSQL, MySQL, and MongoDB to enhance query performance. It explains the syntax and benefits of indexing specific JSON paths, and lists supported database systems.
