Merged
Conversation
…als on ILIKE wildcards (JasperFx#4169) Co-Authored-By: Claude <noreply@anthropic.com>
…n ILIKE wildcards (JasperFx#4169) StringEqualsIgnoreCaseFilter now implements ICompiledQueryAwareFilter so parameter matching uses the raw value and ILIKE escaping is deferred to runtime in the generated code. Closes JasperFx#4169 Co-Authored-By: Claude <noreply@anthropic.com>
…/StartsWith/EndsWith (JasperFx#4169) Co-Authored-By: Claude <noreply@anthropic.com>
…h/EndsWith helpers (JasperFx#4169) The ContainsString(), StartsWith(), and EndsWith() helpers in compiled query base classes were not escaping %, _, and \ before wrapping with LIKE wildcards, causing user values containing those characters to be treated as SQL wildcards at runtime. Co-Authored-By: Claude <noreply@anthropic.com>
…ery (JasperFx#4169) Compiled queries using Select projections hit StatelessCompiledQuery which has StartsWith and EndsWith helpers swapped, causing prefix matches to behave as suffix matches and vice versa. Co-Authored-By: Claude <noreply@anthropic.com>
… and ComplexCompiledQuery (JasperFx#4169) StartsWith() returned a suffix pattern (%value) and EndsWith() returned a prefix pattern (value%) in both classes, causing compiled queries with Select projections or Includes to match the wrong end of the string. Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Author
|
Test failures look to be either preexisting or flaky test for the single timing related one, but do double check on your side. Tests pass locally for me. |
Member
|
The LINQ failure is not related, I've got this from here |
This was referenced Mar 16, 2026
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
2 participants
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.
Fixed #4169 and related issues.
Co-authored with Claude Code - Opus 4.6
Verified existing tests still pass.
Note: This changes existing behaviour by fixing a bug where a % or _ in StartsWith, EndsWith and Contains is now no longer treated as a Wildcard. If people were relying on this behavior this might be breaking for them. This would however be relying on undocumented and unexpected behaviour. Just wanted to mention it.