Gavin, In response to your comment on my weblog - seem comments below...
> unsaved-value="null" makes no sense for composite-ids or any other kind of > "assigned" id. Thats because the identifier property is *never* null when > Hibernate gets to it. > > Now, I'm assuming that what you *really* want is for an update() to be > cascaded from Parent to Child. In that case > > (1) call update() on the Parent > (2) Have the collection configured with cascade="all" > (3) have the Child mapped with unsaved-value="none" > > Then it should work just right. > > HOWEVER: I have just spotted a bug in Hibernate 1.2.x that causes > unsaved-value to be ignored for composite-ids. Has this been fixed in CVS - or can you tell me where to fix it in 1.2.2? Is it large enough to warrant a 1.2.3 release ;-) > > A simple oversight in the map parsing code. > > So I apologise if you wasted time on this it was a staightforward little bug. > I don't consider it a waste of time if I can get a fix today - I'd rather it be a bug than me an idiot :-) I'm glad I found it and was able to reproduce it - hopefully making Hibernate easier to use for someone else. Thanks, Matt > Gavin ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
