because queries are generated depending on the mappings, would be very useful if you can attach mappings and classes to recreate your issue, then, hopefully your issue will have more attention. Please have a look to the WELCOME message on the top left corner of: http://216.121.112.228/secure/Dashboard.jspa
<http://216.121.112.228/secure/Dashboard.jspa>Thanks. On Mon, Nov 29, 2010 at 4:17 PM, Brian Berns <[email protected]> wrote: > I have discovered what seems to be a major bug in the way that HQL > parameters are converted into SQL. I've reported it (http:// > 216.121.112.228/browse/NH-2415), but it's received no attention so > far. Can anyone help me locate the developer responsible for the > processing of the HQL parse tree into SQL? > > In a nutshell, it appears that the SQL generator rearranges the > expressions in the where clause. If these expressions contain > parameters, then the parameters end up with the wrong values. > > Note that this also affects the result of Linq queries in NHib 3.0, > because they are now processed via HQL parse trees as well. > > Bottom line: I'd like to get some attention on this bug, but I don't > know where to start. Can anyone point me to a NHib core developer who > might be interested? Thanks. > > -- Brian > > -- > 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]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- Fabio Maulo -- 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.
