I have a property mapped with a SQL formula. I can sort on that property as expected. However, if I have any bag collections marked lazy="true" and fetch="subselect", then a SQL exception is thrown. It appears to be putting an extra ORDER BY in the subselect that is generated to load the lazy collection, giving:
The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless TOP or FOR XML is also specified If I change it to fetch="select", it works fine; if I sort on a non- formula property, it works fine; if I set the collections lazy="false" it works fine. It this something inherent in subselect collection mapping? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
