Repository navigation
Fix IF() condition evaluation
#518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift
🔎 Supported by static analysis
🏁 Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 8621
🏁 Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 7495
🏁 Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 41275
🏁 Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 12372
🏁 Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 389
🏁 Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 24303
🏁 Script executed:
Repository: WordPress/sqlite-database-integration
Length of output: 10958
Preserve the string result type of mixed-type
IF()expressions.translate_runtime_function_call()emits a raw SQLiteCASE. ForIF(1, 2, '3') = '2', SQLite evaluates the selected branch as an integer, so the predicate returns false. MySQL treats theIF()result as a string when either result branch is a string, so the same predicate returns true.Apply the type coercion outside the
CASEso branch evaluation remains lazy. Add a regression test forIF(1, 2, '3') = '2'.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a valid, pre-existing type-conversion gap that also affects
CASEandIFNULL(). A text cast fixes this example but breaks some numeric comparisons. I’ll keep this PR focused on #517 and leave mixed-type handling to separate work building on #508.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JanJakesThanks for the clarification. Keeping this PR focused on#517makes sense. The suggested text cast is not a general fix because it can break numeric comparisons.Would you like me to open a follow-up issue for mixed-type handling in
IF(),CASE, andIFNULL(), building on#508?✏️ Learnings added
You are interacting with an AI system.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there is no such issue yet, open it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 32003
🏁 Script executed:
Length of output: 2797
@JanJakesI found no existing issue for this gap. Created#519and assigned it to you.The issue covers mixed-type handling for
IF(),CASE, andIFNULL(), building on#508. It includes your earlier clarification that an unconditional text cast is not a general fix.🧠 Learnings used
You are interacting with an AI system.