[nhibernate-issues] [NHJIRA] Commented: (NH-2317) Select after Take does not work properly

[Stefan W. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21158#action_21158 ] 

Stefan Wenig commented on NH-2317:
----------------------------------

I can't see a situation with a semantic difference between take + select and select + take. If the two queries that Fabio provided don't return the same results, I'd question the accuracy of at least one of them. So I'd say swithing consecutive Take and Select calls is OK.

But why would you want to do this? As soon as anything gets between Take and Select, you'll have to go the other path anyway. If you have a good way to specify it "right" in HQL, such as the sub query (from Artists take 3), I'd take it. 

> Select after Take does not work properly
> ----------------------------------------
>
>                 Key: NH-2317
>                 URL: http://216.121.112.228/browse/NH-2317
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.0.0.Alpha2
>            Reporter: Jose F. Romaniello
>            Priority: Major
>         Attachments: NH2317.7z
>
>
> artists.Take(10).Select(a => a.Id) throws exception on 
> NHibernate.Hql.Ast.ANTLR.PolymorphicQuerySourceDetector.GetClassName(IASTNode querySource) en PolymorphicQuerySourceDetector.cs: line 62
> artists.Select(a => a.Id).Take(10) works properly
> These two queries work with the old provider.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira