Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • M mariadb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • mariadb
  • Repository
  • mariadb
  • sql
  • sql_select.cc
Find file BlameHistoryPermalink
  • gkodinov/kgeorge@macbook.gmz's avatar
    Bug #25551: inconsistent behaviour in grouping NULL, depending on index type · 2ba683f2
    gkodinov/kgeorge@macbook.gmz authored Jan 31, 2007
     The optimizer takes away columns from GROUP BY/DISTINCT if they constitute
     all the parts of an unique index.
     However if some of the columns can contain NULLs this cannot be done 
    (because an UNIQUE index can have multiple rows with NULL values).
     Fixed by not using UNIQUE indexes with nullable columns to remove
     grouping columns from GROUP BY/DISTINCT.
    2ba683f2
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7