From: Daniel G. (JIRA) <nh...@gm...> - 2011-04-20 16:29:34
|
Linq provider overcaching HQL ----------------------------- Key: NH-2658 URL: http://216.121.112.228/browse/NH-2658 Project: NHibernate Issue Type: Bug Components: Linq Provider Affects Versions: 3.1.0 Reporter: Daniel Guenter Priority: Major The linq provider caches a query assuming that ALL constants will be turned into HQL parameters. Sometimes this is not the case. A linq extension that selects a concrete entity property based on a constant value will never pass that value into HQL. This is also a blocking issue in getting Linq to work with dynamic-components. The string value passed into the dictionary (dict["key"] == x) cannot be passed to HQL as a parameter as it is directly evaluating a property name. Thus the first query will work but subsequent queries will be wrong and will reuse the column/property name of the first cached query. -- 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 |