No, the parameter size should be fixed. That ensures that you have consistent query plans. Specify that the field type is StringClob in the mapping
On Tue, Oct 5, 2010 at 9:54 PM, srf <[email protected]> wrote: > I was trying to figure out why things working working anymore in > nhibernate 3 and noticed that in nhibernate 2 the dbparameter.size > would be set to what the dbparameter.value's length was as long as the > dbparameter.size was set to 0. Now in nhibernate 3, the > dbparameter.size is getting set because line 164 in SqlClientDriver.cs > is commented out so its now by default setting the size to some fixed > size rather than setting the size to what the parameter value size is. > So I was wondering why that is commented out now. The problem I have > is that I have varchar(max) values and the parameter size could be > really large so the parameter size need to be set to what the length > of the text inserted or sqlserver will just cut it off to whatever the > parameter.size is. Is handling really large text like varchar(max) to > be done differently? > > thanks > > scott >
