Its possible to supply the checks like nullable="false" in orm.xml or jpa annotations or hbm xml for entity fields.
Let us say we are coding to a system which is already live and generating the DDL on production is a big no no.
Meaning the actual DDL sql is hand crafted.
In all likelihood the actual ddl would also have a similar not null in its sql.
Question is this: Are we making the Java layer do too much work when the not null check is already there in the database for the column in the table?

Any thoughts?
If we try to insert null data the database would have prevented it because of the not null. The nullable="false" is that not an overhead on the java layer?

As far as I know this setting is not used by any other mechanism than DDL generation and bean validation. Since you don't use both, you might not have a problem with performance or other side effects. I would keep it in the code just to have it as a helping documentation.

How can one turn off the validation that will be done on the bean?
Is there any way available or is the only way to do that removng nullable="false"

Bean validation is not activated by default, so you don't need to do anything:
http://docs.jboss.org/hibernate/stable/ ... e/#d0e3875

It seems to be on.

Caused by: org.hibernate.PropertyValueException: not-null property references a null or transient value: org.somedomein.entities.User.lastName

Maybe thats because am using spring with the jpa.

I dont really mind it being on. But would like to know how to turn it off?

It seems to be on.

Caused by: org.hibernate.PropertyValueException: not-null property references a null or transient value: org.somedomain.entities.User.lastName

Maybe thats because am using spring with the jpa.

I dont really mind it being on. But would like to know how to turn it off?

I don't really think you can turn some of the basic checking off. You can control if you get an exception or not by changing the nullable="false/true" option. If you are worried about performance (as the original post seems to indicate) I think it is better to get an exception before everything is sent to the database which requires a lot more time.

Agreed.
That sounds all right.

I have posted a similar question about CascadeType.DELETE.
If you get time have a look at it.

viewtopic.php?f=1&t=1009904