You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to v8, these same efcore queries now map to stringValue LIKE '%value%'.
This doesn't break the queries per say, but it did break our index usages. We had several indexes that used the strpos to mirror the npgsql efcore query mapping, and those all needed to be updated.
I don't think this constitutes a breaking change. Yes, if you have an expression index, a SQL translation change would cause it to no longer get used, but there's very little that doesn't constitute a breaking change at that point...
Prior to v8, our efcore queries that utilized
stringValue.Contains(value)
mapped to:strpos(stringValue, value) > 0
.This is documented here: https://www.npgsql.org/efcore/mapping/translations.html.
After upgrading to v8, these same efcore queries now map to
stringValue LIKE '%value%'
.This doesn't break the queries per say, but it did break our index usages. We had several indexes that used the
strpos
to mirror the npgsql efcore query mapping, and those all needed to be updated.This can cause havoc on a production database.
Could we get the documentation updated here? https://www.npgsql.org/efcore/mapping/translations.html
And list it as a breaking change?
The text was updated successfully, but these errors were encountered: