http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce Classic : IdFixUp won't fix up grandChilds Fri, 17 Apr 2026 01:40:00 -700 Tue, 18 Sep 2007 14:11:03 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=433 http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ http://www.ideablade.com/forum/forum_posts.asp?TID=433&PID=1203#1203 Author: Dominique
Subject: 433
Posted: 18-Sep-2007 at 2:11pm

Hi,
I have 3 tables, parent - child - grandchild.
Parent has an autoincrement id as a PK
Child use id and an ean-number as a PK (all wrong, compound key _and_ natural key :-))
GrandChild, which holds lines for childs uses id, ean and lineNumbers as a PK.
I create some parent entities and I see that devForce give them a negativ id.
The problem arise when I save my entities. The id in parent and child get fixed but not the one in the grand child and this lead to a constraint violation.
As a work aroud I use a "ForceIdFixUp" after the creation of the Parent entities.
Extra info: I am working on the serverside but the persistance manager originate from a smart client which called a ServerRpcPersistenceDelegate through the BOS.

Am I missing something?

]]> Tue, 18 Sep 2007 14:11:03 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=433&PID=1203#1203