-
Notifications
You must be signed in to change notification settings - Fork 3.3k
#18132 Added regression tests for concatenating int and strings together #19948
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
#18132 Added regression tests for concatenating int and strings together #19948
Conversation
@@ -242,6 +242,17 @@ public override Task Complex_nested_query_doesnt_try_binding_to_grandparent_when | |||
|
|||
public override Task AsQueryable_in_query_server_evals(bool async) => null; | |||
|
|||
public override Task String_int_concat(bool async) => null; |
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.
I had to null off this test in SQLite as it fails the result verification. The query produces <orderId>
but the expected results are <orderid><customerid>
. The other frameworks seem to handle this fine. Is this expected?
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.
it's a bug in sqlite - whenever possible we should be returning results matching Ling to Objects
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.
we should be using ||
operator for string concat in this case
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.
filed #19990
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.
@Muppets - we looked at the issue briefly with @smitpatel and it's potentially quite a complicated problem to fix properly. So for now, you can just skip the test on sqlite using 19990 as reason (rather than null it out)
@Muppets some other cases you can consider: one argument being a parameter, also some tests with reversed order (string + int rather than int + string) |
259d299
to
5ce1b7d
Compare
@dotnet/aspnet-build - Is running helix test for community PRs not allowed?
|
@Muppets thanks for the contribution! |
Summary of the changes
Fixes #18132