Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 78965 invoked from network); 16 Dec 2003 21:52:05 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Dec 2003 21:52:05 -0000 Received: (qmail 16506 invoked by uid 500); 16 Dec 2003 21:51:52 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 16389 invoked by uid 500); 16 Dec 2003 21:51:52 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 16370 invoked from network); 16 Dec 2003 21:51:51 -0000 Received: from unknown (HELO mail.gmx.net) (213.165.64.20) by daedalus.apache.org with SMTP; 16 Dec 2003 21:51:51 -0000 Received: (qmail 26472 invoked by uid 65534); 16 Dec 2003 21:51:55 -0000 Received: from adsl-62-167-28-119.adslplus.ch (EHLO gmx.ch) (62.167.28.119) by mail.gmx.net (mp014) with SMTP; 16 Dec 2003 22:51:55 +0100 X-Authenticated: #15507884 Message-ID: <3FDF7E71.4090703@gmx.ch> Date: Tue, 16 Dec 2003 22:51:45 +0100 From: Jakob Braeuchi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: OJB Developers List Subject: Re: [BUG?] In order of FK description @ References: <39330.10.0.0.5.1071525415.squirrel@ags01.agsoftware.dnsalias.com> In-Reply-To: <39330.10.0.0.5.1071525415.squirrel@ags01.agsoftware.dnsalias.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N hi antonio, do you have an sql ready ? jakob Antonio Gallardo wrote: > Hi: > > I found the follwing problem. I am not sure if this is a bug or lack of > documentation. Anyway, I think we need to see this: > > I have a 2 fields Primary Key (PK) on a class A defined as follow: > > > column="ID_A" jdbc-type="INTEGER"/> > column="ID_B" jdbc-type="INTEGER"/> > auto-update="false" auto-delete="false"> > > > > > > Please note the order how are defined the PK. First is id_1 then id_2! Now > the secodn class: > > > column="ID_A" jdbc-type="INTEGER"/> > column="ID_B" jdbc-type="INTEGER"/> > column="ID_A" jdbc-type="INTEGER"/> > auto-update="false" auto-delete="false"> > > > > > > Seems like the order of the defined inverse-foreign keys is very important > (not documented at all website) since if in the sample we change the > "order" of id_1 and id_2 in both above describe just in > the of class A and the of > class B We got an referential integrity error, reference from B not found > in A! > > Note the order of fields in class B, (first id_2, follow id_1) they are > intentionally changed as they are in class A. > > I hope the problem is good explained, if not please let me know. I will > try to explain it better. > > Best Regards, > > Antonio Gallardo > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org > For additional commands, e-mail: ojb-dev-help@db.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org