You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2021/01/09 15:58:00 UTC
[jira] [Updated] (IGNITE-13754) .NET: LINQ provider emits incorrect
table alias for queries with JOIN and GROUP BY combined
[ https://issues.apache.org/jira/browse/IGNITE-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-13754:
------------------------------------
Fix Version/s: 2.10
> .NET: LINQ provider emits incorrect table alias for queries with JOIN and GROUP BY combined
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-13754
> URL: https://issues.apache.org/jira/browse/IGNITE-13754
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET
> Fix For: 2.10
>
> Attachments: Meeting.cs, MeetingAttachment.cs, Program.cs
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See the attached reproducer. Generated SQL is:
> {code}
> select _T0.MEETINGID, max (_T0.AttachmentDate) from USERSCHEMA.MEETING as _T0 inner join USERSCHEMA.MEETINGATTACHMENT as _T1 on (_T1.MEETINGID = _T0.MEETINGID) group by (_T0.MEETINGID)
> {code}
> {{_T0.AttachmentDate}} should be {{_T1.AttachmentDate}} here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)