The blog author posted a comment on the blog indicating that the team was using NHibernate 2.1.0 with MSSQL Server 2005. I will try to test 2.1.1 when time allows.
Fabio, do the fixes you made negate the need for setting prepare_sql = true? The reason why I ask is that if I'm understanding the blog correctly, using prepare_sql is the wrong way to solve the problem as SQL server is going to cause the execution plan per connection behavior. On Oct 26, 8:29 pm, Daniel Auger <[email protected]> wrote: > I've sent messages to both the blog poster and the initial reporter to > validate the fix and report back here. > > On Oct 26, 6:13 pm, Fabio Maulo <[email protected]> wrote: > > > Use 2.1.0 and then let me know... > > I don't remember exactly where I have fixed all parameters-size stuff but > > should be 2.1.0 or in the actual branch (2.1.1 that will be released > > on Sundays). > > > 2009/10/26 Craig van Nieuwkerk <[email protected]> > > > > 2.0 it says in the article. Could be 2.01, it is not specific. > > > > On Tue, Oct 27, 2009 at 9:39 AM, Fabio Maulo <[email protected]> wrote: > > > > NH version? > > > > > 2009/10/26 Daniel Auger <[email protected]> > > > > >> This came across my twitter stream today: > > > >>http://www.objectreference.net/post/NHibernate-and-Execution-Plans.aspx > > > > >> The blog entry claims that prepare_sql = true really only solves the > > > >> problem on a per connetion basis. > > > -- > > 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 -~----------~----~----~----~------~----~------~--~---
