Hibernate boolean field mapping issue

Question

There is a boolean field in Entity :

@Column(name = "FREEFLAG", columnDefinition = "NUMBER(0,1) default 0", nullable = false)    
public boolean getFreeflag() {
   return freeflag;
}

database - Oracle, field FREEFLAG - NUMBER(0,1)

I try to get object from db with Hibernate, but if the field in db is null i got a exception :

Exception in thread "main" org.hibernate.PropertyAccessException: Null value was assigned to a property of primitive type

Why default value doesn't work ? How I can resolve this problem on server side? I have to have 0 or 1 value in db.

I got the solution - Default value not working in hibernate. But I still have to modify database. I have added DDL - alter table client modify freeflag default 0 not null DML - update client set freeflag = 0 where freeflag is null; commit

Is there data already in the database? The default in the database default on _storing_ the entity, not the Java default on loading. — Boris the Spider, Jul 12 '14 at 09:15
Yes, free flag in db is null.I can have null value in db, I don't have to change db settings. Can I set default value when i get value from db ? — idmitriev, Jul 12 '14 at 09:35
You can edit the setter to set `false` if `null` is sent - but this is a hack. The setter would need to be `Boolean` rather than `boolean`. — Boris the Spider, Jul 12 '14 at 09:37
This is ORM - you are mapping the state of the DB to your POJOs. If the database allows `NULL` then you will have to allow `null` in your POJO too. — Boris the Spider, Jul 12 '14 at 09:39
Hm.. It's clear, I thought that I can set default value to field on server side. Thanks Boris — idmitriev, Jul 12 '14 at 09:46
Same problem is solved [here][1] in stackoverflow check for it. [1]: http://stackoverflow.com/a/13594108/3828557 — Muhammad, Jul 12 '14 at 11:42
Muhammad sorry, but I have Oracle DB with appropriate consequences — idmitriev, Jul 12 '14 at 12:23
columnDefinition = "NUMBER(0,1) default '0'" can you try with this single quote '0' syntax. — Bhushan, Jul 12 '14 at 12:38
Yes, I have tried, doesn't matter, nothing happened. Actually columnDefinition doesn't work. — idmitriev, Jul 12 '14 at 14:12
I GOT THE SOLUTION - http://stackoverflow.com/questions/21983230/default-value-not-working-in-hibernate — idmitriev, Jul 13 '14 at 16:32

score 1 · Answer 1 · answered Jul 13 '14 at 12:55

In one of your comments you have said that your database allow null values for this column. The columnDefinition attribute is used by JPA Provider during schema generation process, so I can assume that you have not generated schema after you added columnDefinition attribute (nor nullable=false). Hints in columnDefinition which set default value were not applied to database, so it's nothing strange that you don't have this column defaulted.

Another way you can make it work is creating custom Converter for this field, which will save values in the way you need. More informations about converters implementation available here.

score 0 · Answer 2 · answered Jul 12 '14 at 12:46

0

The columnDefinition is database dependent and hence might cause issues sometimes. What I got from searching on net is that it works sometimes but doesnt work in some cases. An alternative is to use the prePersist method technique described in below link:

http://www.coderanch.com/t/450124/ORM/databases/entity-Boolean-field-default

Hope this helps.

answered Jul 12 '14 at 12:46

Inder

160
9

Thx, but this is hack I think. Actually I can add logic to my getter : @Column(name = "FREEFLAG",nullable = false,columnDefinition = "boolean default true") public Boolean getFreeflag() { if (freeFlag == null) return false; return freeflag; } but I dont like this approach. – idmitriev Jul 12 '14 at 14:13

Hibernate boolean field mapping issue

2 Answers2