Auto truncate on Entity VS Mapping

[Johan Spännare]

I resently upgraded to FHN 1.2 (HN3). After the upgrade i noticed that NH or FNH is truncating the values to fit the Length set in the mappings. Before the upgrade the incorrect value was sent to the database and an SQL Exception was raised. But since NH or FNH now truncating the value before sending it to the database. No exception is fired.

NOTE

If you use NH Profiles you can see the incorrect value. But if you profile the database the incorrect value is "fixed" and is set to the max length set in the mappings.


Is this a bug or "feature" that can be disabled?

Best reg
Johan