Doc: clarify "p" field example #2
Merged
Conversation
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
I thought it was referring to a column name.
CDThomas
approved these changes
Sep 25, 2024
tobyhede
pushed a commit
that referenced
this pull request
Oct 27, 2025
…le-clearer Doc: clarify "p" field example
tobyhede
added a commit
that referenced
this pull request
Oct 30, 2025
Add ilike_operator_case_insensitive_matches test covering ~~* and ILIKE operators. This addresses the coverage gap identified in the review where case-insensitive LIKE variants (lines 42-75 in original SQL) were not migrated. Adds 6 assertions testing both ~~* and ILIKE operators across 3 records. Addresses FINAL_CODE_REVIEW.md recommendation #2 (P2).
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.
I thought it was referring to a column name.