Hibernate version: 3.1

Name and version of the database you are using: Oracle 10g

Hi,

I need to know exactly how hibernate behaves in the following situation:

Note that all interactions with the database are read-only.

I have a column of size 30 correctly mapped in Hibernate. If the size is altered in the base but not in the mapping, will it result in an error when attempting to run Hibernate?

If no error occurs, what happens if the new size is smaller? And if it's bigger?
I'm guessing that if the new size is 32, if I try to query a value that's too large from it, Hibernate will truncate it.

Would it be wiser to omit the size from the mapping and let Hibernate deal with it?

I need to know what happens for both NUMBER/Big Decimal values and VARCHAR2/String values.

Thanks in advance.

I think Hibernate in general ignores any size attributes in the mappings. It is only used by the schema-generation tool that can be used to generate the SQL that creates the database for you.

I guess the behavior depends on how Oracle is handling such things. I am mostly using MySQL and PostgreSQL and I think MySQL silently crop strings when inserting data while PostgreSQL fails (or maybe it was the other way around...).

Thank you for the answer.