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_class.cc
Find file BlameHistoryPermalink
  • gshchepa/uchum@gleb.loc's avatar
    Fixed bug #28076: inconsistent binary/varbinary comparison. · 0aabb89e
    gshchepa/uchum@gleb.loc authored Nov 10, 2007
    After adding an index the <VARBINARY> IN (SELECT <BINARY> ...)
    clause returned a wrong result: the VARBINARY value was illegally padded
    with zero bytes to the length of the BINARY column for the index search.
    (<VARBINARY>, ...) IN (SELECT <BINARY>, ... ) clauses are affected too.
    0aabb89e
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7