Detect another form of mysql computed columns - #30
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the MySqlConnector provider’s schema inspection so MySQL columns with ON UPDATE ... behavior are detected as database-generated/read-only, supporting the Issue #28 use case of excluding these columns from write statements while still mapping them on reads.
Changes:
- Extend computed/generated column detection in
INFORMATION_SCHEMA.COLUMNSparsing to treatEXTRAcontainingON UPDATEas computed. - Refactor the computed detection SQL expression to a multi-branch
CASEfor additional patterns.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
rhuijben
force-pushed
the
fix/mysql-on-update-computed
branch
from
February 19, 2026 09:12
500bca7 to
1cd0ca9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Attempt at fixing issue #28