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
Run the following query (includes the line-endings)
SELECT*FROM table
WHERE name1 = @name1
AND name2 = @name2
Description
If a named variable is followed by Windows CRLF style line endings, the variable name will include the \r portion of the line ending which causes the variable lookup in the namedMap to fail. In my PR, I've updated the expression builder to look for \r in addition to \n.
Workaround
Put a space after the named variable so that there's a separator from this list of supported separators between the named variable and the CRLF line ending.
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨
GORM Playground Link
I've created a PR with test cases instead.
To Reproduce
Run the following query (includes the line-endings)
Description
If a named variable is followed by Windows CRLF style line endings, the variable name will include the
\r
portion of the line ending which causes the variable lookup in thenamedMap
to fail. In my PR, I've updated the expression builder to look for\r
in addition to\n
.Workaround
Put a space after the named variable so that there's a separator from this list of supported separators between the named variable and the CRLF line ending.
gorm/clause/expression.go
Line 130 in 7496c3a
The text was updated successfully, but these errors were encountered: