I recently upgraded from NHibernate 2.1 to 3.1.  I am having a problem
with NHibernate truncating my nvarchar(max) columns.  This post
describes my situation perfectly:
http://www.primordialcode.com/Blog/Post/nhibernate-prepare_sql-considerations-mapping-long-string-fields.

The current behavior seems to me to be a bug.  If I give a simple
mapping:

   <property name"LargeString" />

And the there is a column "LargeString" in the database with an
nvarchar(max) data type, it would be defective behavior to truncate
data retrieved by that column to 8000 characters.  But that is exactly
what 3.1 does.

Could someone give me direction on how to handle this?

-- 
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.

Reply via email to