Hi all,

We are using Hibernate 3.0.5 in an ongoing project. Our backend database is Oracle 9i (9.2) hosted on a RedHat Linux machine.

The other day a developer found out that a not-null column is accepting null values with no problem. However in the Hibernate hbm file the column is defined as being not-null. It's possible when the schema was first generated this column wasn't not-null. However we are using the auto update feature so the schema has to be updated when there's a change.

So, first we thought that the SchemaExport is not working correctly. However I ran it in the console and the generated DDL statements were correct (the column was not-null).

So this might be a schema update problem. The truth is that that column contains a few null values so the schame update most fail but no exception or warning message is being thrown. However we can see the correct warning messages for other updates that cannot be applied (i.e. already present referential integrity constraints).

Any ideas what could be wrong?