How do I handle tables with columns with default values?

Blackbrrd · **Joined:** Wed Sep 28, 2005 6:45 pm **Posts:** 56

I am using Hibernate with annotations.

I have table like this

Code:

CREATE TABLE etel.torderstatussnap
(
  orderstatussnapid int4 NOT NULL DEFAULT  nextval(('etel."torderstatussnap_id_seq"'::text)::regclass),
  orderstatussnap_orderid int4,
  orderstatussnap_statusid int4,
  orderstatussnapdate timestamptz DEFAULT now(),
  id_contact_handler int4
);

If I set the orderstatussnapdate column to insertable = false the default value, now() will be set in the database, but the data isn't read back into the object...

I want to use the databases now() since I am connecting to the database several places and not using hibernate on all those places either.

So, how should I handle this?

Surely somebody must have had the same problem?

Thanks in advance for any help!

batmat · **Posted:** Fri Jul 07, 2006 10:11 am

I don't know exactly the behaviour of this now. But maybe it's analogous to the trigger one.

Try the session.refresh() method on your object after saving it. It should be OK.

hlfsousa · **Posted:** Fri Jul 07, 2006 12:53 pm

That default column generator works just like an 'identity' column, so I guess generator="identity" would work just fine.

Blackbrrd · **Joined:** Wed Sep 28, 2005 6:45 pm **Posts:** 56

that looks like two helpful hints, I will look into both answers later. Thanks :)

session.refresh(object); did indeed refresh the object, just gotta call session.flush() first! ;)

It doesn't completely resolve the problem, but it helps :)

I am wondering if setting columns with default values to not insertable is a good option... It does atleast sound ok...

Now I am just wondering what I should do with situations where I only want to update some of the fields of a class... Probably I will have to use hql... A bit annoying to have to write 20 lines of code instead of one to update an object....

I could maybe have used dynamic updates, but then again, I would have to write hql for all those situations where I want to write a field with null to the database....

It would be close to optimal if I could turn on/off dynamic updates, but I think I would need to SessionFactory objects, which would be a complete mess :P