[b]Hibernate version:1.2.0 beta1

[b]Name and version of the database you are using:SQL 2005

Hello all,

I have read a article some where about this..

there is a slight difference in what the two will do

<property type="String(50)" ... /> will create an IDbDataParameter that has
a length of 50 - so if you try to put a value of longer than 50 chars in
there it will truncate it.

<property type="String" length="50" .../> will create an IDbDataParameter
that has the max length of a nvarchar field in ms-sql - 4000. The attribute
length is in there for schema export and is not used to build the parameter.



I like this setting <property type="String(50)" ... />, which will truncate a value lnger than 50..

I write my mapping as following...

<property name="Name" access="property" type="String(32)">
<column name="Name" not-null="true"/>
</property>

and give a value than is longer than 50 characters...(it's supposed to truncate it and store to db, right?) There is a sql exception about a value is too long....why?

even though I write the mapping in this way, it still won't truncate the string value...

<property name="Name" access="property" type="String(32)">
<column name="Name" not-null="true" sql-type="nvarchar(32)"/>
</property>

It depends on the database, but silent truncation of values is dangerous so you should be glad MS SQL doesn't do it.

would you mind that I am asking why that's dangerous??

In some scenarios, that's very useful..
I don't need to substring value of string type before insert to db..

It's dangerous because if you are using MySQL for example (it truncates string values), it's very easy for this truncation to happen when not intended, causing data loss that you might not even notice for some time.

If an exception happens when the data is oversized, you will notice it immediately. And there's a classic rule that says the earlier you detect a problem, the easier and less expensive it is to fix.