Hibernate version:2.1.6

Name and version of the database you are using:Oracle 9



Im trying to import data from an old DB schema into my new Hibernate backed DB schema.

When I come to save the objects, Im getting a whoole series of "Missing IN or OUT parameter at index '4').

This particular value is nullable, yet Hibernate is issuing a full insert statement, with 11 parameters and 11 question marks, and according to the Hibernate log info just prior to the attempted SQL insert, it only binds parameters to all the non-null fields (param index 1,2,3,8,9,10,11).

However, Oracle seems to be requiring that we set something for all the nullable fields, or at least tell the prepared statement that we have null fields. (Fields 4,5,6,7 are all mapped as nullable in the mapping docs)

Is this a known issue, and if so, how do I get Hibernate to shut Oracle up?

Im using <id> generator type = assigned (which Im going to switch out to sequence after the legacy import).


Nick

Ok, I figured it out.

I had a custom data type in use, and I wasnt actually setting a parameter in the case when the object had a null property

my custom user type had:

if( value != null )
{
Hibernate.DATE.nullSafeSet( ... )
}