What is wrong with this HQL query in version 2.1.2.4 of NHibernate? -
After
then throwing an Antlr.Runtime.NoViableAltException below the HQL query. I was able to determine that this issue is with the member. If the member is removed then the name by order from the query. Will be executed. This HQL has worked fine in an earlier version of NHibernate, but it broke with the upgradation of 2.1 2.1.4.4 NHibernate. How can I be a member without throwing an exception? Any help is greatly appreciated. Thanks!
ChartAssignmentLogRecord chartAssignmentLogRecord from the inclusion Indicator joining the inner measure.ProviderLocation of the chartAssignmentLogRecord selection chartAssignmentLogRecord.Measure joining the provider as the provider ProviderLocation.Provider provider ProvidersLocation.Address As a member joining the measure.Member joining the address of the address where the chartAssignmentLogRecord.AssignedDate & gt; =: STARTDATE and chartAssignmentLogRecord.ChartModifiedStatus =: modifiedStatus and chartAssignmentLogRecord.AssignedDate = (select max (subChartAssignmentLogRecord.AssignedDate) from ChartAssignmentLogRecord subChartAssignmentLogRecord where subChartAssignmentLogRecord.Measure = chartAssignmentLogRecord.Measure) ordered by chartAssignmentLogRecord.AssignedDate desc, provider.LastName, address. Thanks to DanP, I used the Measure. Address: Line 1, member.LastName
Member instead of Member.ListName. In the order of ListName by clau. Definitely why this is not certain, as far as I know, my HKLL should have been valid and definitely valid in earlier versions of NHibernate.
Comments
Post a Comment