Hi,

I have a field in SQL DB as integer type; so i have kept int type property in my model to hold the values.

But the field in the DB can have value "NULL" since it is optional field. When i run select query and try to save in the MODEL, i am getting following error.

"PropertyAccessException: Null value was assigned to a property of primitive type setter"

I have kept the following code on top of the field.


@Column(nullable=true)
int uiAdjId;

Still i am getting same error.

Please help me to resolve this.

Thanks,
Laks

The only way I know to get around this is to have an java.lang.Integer field in your object. That way it is an object reference that can be null. You get still have a getter/setter that take and return primitive values (i.e., int) so these change is isolated. You just map the column to the private Integer field.

Hi,

It is working fine.

Thanks for your assistance.

Laks,

When I'm creating an Entity and I have to choose between Long or long, what should I consider?
Is there any more than just considering if I need a nullable / not nullable column?

Thanks

I tend to like primitive mutable data (i.e., long) rather than non-mutable objects (i.e., Long) but it probably makes little difference unless you are working with very large volumes of data. Every time you assign value to a Long or modify the value of a Long (a new Long object is created) so you have more garbage collection overhead. Again, it probably doesn't matter much unless you have very large data volumes. My background is with performance measurements which tend to be very voluminous thus explaining my bias for primitive data.