Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • CiviCRM Core CiviCRM Core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,460
    • Issues 1,460
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • CiviCRM CoreCiviCRM Core
  • Issues
  • #2381
Closed
Open
Created Feb 12, 2021 by DaveD@DaveDMaintainer

Trigger-based logging crashes on updates to tables with fields of type blob

In https://github.com/civicrm/civicrm-core/pull/18782 binary comparison was added to triggers to allow it to capture changes in upper/lower/accents. For reasons I don't understand at the moment if you apply binary collation to a binary field (like blob) it says binary doesn't match binary.

COLLATION 'utf8mb4_bin' is not valid for CHARACTER SET 'binary'

Description may change as I look closer. Marking regression since it was added in 5.35. Comes up when doing e.g. UPDATE civicrm_file SET ..something.. which has document as a blob field.

Edited Feb 12, 2021 by DaveD
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking