-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: Composite-id with unsaved-value
PostPosted: Wed Apr 12, 2006 4:11 pm 
Senior
Senior

Joined: Fri Jan 13, 2006 2:50 pm
Posts: 123
Location: Blumenau / SC / Brasil
Hi.

1. Is it possible to use composite-id with unsaved-value option?

2. I'd like to use the method SaveOrUpdate, I think this (using unsaved-value) is the only way, right?

I have read about it in the NHibernate Help, but I just have found this:

Quote:
unsaved-value (optional - defaults to none): Indicates that transient instances should be considered newly instantiated, if set to any.


I didn't understand.

3. This means that every time the NH will generate an Insert SQL when I call SaveOrUpdate?

Thanks!


Top
 Profile  
 
 Post subject: Re: Composite-id with unsaved-value
PostPosted: Thu Apr 13, 2006 6:24 am 
Expert
Expert

Joined: Thu Jan 19, 2006 4:29 pm
Posts: 348
mdsrlz wrote:
Hi.

3. This means that every time the NH will generate an Insert SQL when I call SaveOrUpdate?

Thanks!


You should be able to use <version> attribute to tell NHibernate which instances are newly created and which ones need to be updated.

Gert


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.