Matthew Schleindl
2004-10-21 11:26:44 UTC
Hi -
I'm using 2.0 against Oracle 9.1, and Middlegen
appears to be mapping nullable number fields to
primitive java types like 'short', instead of nullable
wrapper types like 'Short'.
The generated hbm.xml's seem to correctly identify
which fields are nullable and which are not: the
non-nullable fields all are marked not-null="true",
the nullable fields omit the non-null attribute, so it
appears to determine field nullability correctly.
I must be doing something really idiotic.
Thanks in advance,
Matt
PS: I get the same result using 2.1
I'm using 2.0 against Oracle 9.1, and Middlegen
appears to be mapping nullable number fields to
primitive java types like 'short', instead of nullable
wrapper types like 'Short'.
The generated hbm.xml's seem to correctly identify
which fields are nullable and which are not: the
non-nullable fields all are marked not-null="true",
the nullable fields omit the non-null attribute, so it
appears to determine field nullability correctly.
I must be doing something really idiotic.
Thanks in advance,
Matt
PS: I get the same result using 2.1