Skip to content

MDEV-24646/MDEV-39711: Fix System-Versioned UPDATE with VIRTUAL columns#5149

Draft
ParadoxV5 wants to merge 1 commit into
10.11from
MDEV-39711
Draft

MDEV-24646/MDEV-39711: Fix System-Versioned UPDATE with VIRTUAL columns#5149
ParadoxV5 wants to merge 1 commit into
10.11from
MDEV-39711

Conversation

@ParadoxV5
Copy link
Copy Markdown
Contributor

@ParadoxV5 ParadoxV5 commented May 31, 2026

UPDATEs on System-Versioned Tables used stale data for Row Format Binary Logging’s after-image, which may be the before-value (MDEV-39711) or even invalidated memory (MDEV-24646).

This is outside of my domain/expertise, so can someöne (human or bot) explain why this 1-liner patch works and is the new mode appropriate?

UPDATEs on System-Versioned Tables used stale data for Row
Format Binary Logging’s after-image, which may be the before-
value (MDEV-39711) or even invalidated memory (MDEV-24646).
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses issues with system-versioned tables and virtual columns (specifically MDEV-24646 and MDEV-39711) by updating the virtual fields using VCOL_UPDATE_FOR_WRITE instead of VCOL_UPDATE_FOR_READ in TABLE::vers_update_fields(). It also adds corresponding replication test cases to verify the fix. There are no review comments, and I have no additional feedback to provide.

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented May 31, 2026

CLA assistant check
All committers have signed the CLA.

@ParadoxV5
Copy link
Copy Markdown
Contributor Author

? do our CLA signatures expire

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants