I think the SchemaExport will still generate a VARCHAR(MAX) in the schema, but persisted changes would need to be less than the specified length (10,000 characters in your example).
On 27 April 2012 07:08, Darren Kopp <[email protected]> wrote: > Wait, are you saying parameter length of 10000 no longer makes the > parameter nvarchar(max)? > > > On Thursday, April 26, 2012 6:20:00 AM UTC-6, FlukeFan wrote: > >> Hi, >> >> I think it will be related to this fix: >> https://nhibernate.jira.com/**browse/NH-2528<https://nhibernate.jira.com/browse/NH-2528> >> >> >> I suspect you'll need to specify the StringClob type in the mapping. >> >> Regards, >> Richard >> >> >> On 26 April 2012 13:14, nfplee <> wrote: >> >>> Hi, i have just upgraded an application to version 3.3.0GA and have >>> notificed a bug when inserting large amounts of data into a NVarChar(MAX) >>> field in the database (also tested with NText). It throws the following >>> error: >>> >>> The length of the string value exceeds the length configured in the >>> mapping/parameter. >>> >>> With the following mapping: >>> >>> <property name="Body"> >>> <column name="Body" /> >>> </property> >>> >>> But it works fine with the following: >>> >>> <property name="Body"> >>> <column name="Body" length="2147483647" /> >>> </property> >>> >>> The original mapping worked fine before. This looks like a pretty bad >>> bug to me. I was wondering if anyone else could confirm this. >>> >>> Thanks >>> >> >>
