Return-Path: 
 <jdo-dev-return-448-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org>
Delivered-To: apmail-db-jdo-dev-archive@www.apache.org
Received: (qmail 60803 invoked from network); 26 May 2005 16:12:42 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 26 May 2005 16:12:42 -0000
Received: (qmail 53535 invoked by uid 500); 26 May 2005 16:12:41 -0000
Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:jdo-dev-help@db.apache.org>
List-Unsubscribe: <mailto:jdo-dev-unsubscribe@db.apache.org>
List-Post: <mailto:jdo-dev@db.apache.org>
List-Id: <jdo-dev.db.apache.org>
Reply-To: jdo-dev@db.apache.org
Delivered-To: mailing list jdo-dev@db.apache.org
Received: (qmail 53517 invoked by uid 99); 26 May 2005 16:12:41 -0000
X-ASF-Spam-Status: No, hits=0.6 required=10.0
	tests=HTML_20_30,HTML_MESSAGE,HTML_TITLE_EMPTY
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from nwkea-mail-1.sun.com (HELO nwkea-mail-1.sun.com) (192.18.42.13)
  by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 26 May 2005 09:12:40 -0700
Received: from phys-mpk-1 ([129.146.11.81])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j4QGCcME008753
	for <jdo-dev@db.apache.org>; Thu, 26 May 2005 09:12:38 -0700 (PDT)
Received: from conversion-daemon.mpk-mail1.sfbay.sun.com by
 mpk-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003))
 id <0IH300E01U8JW4@mpk-mail1.sfbay.sun.com>
 (original mail from Michelle.Caisse@Sun.COM) for jdo-dev@db.apache.org; Thu,
 26 May 2005 09:12:38 -0700 (PDT)
Received: from [129.150.29.79]
 (vpn-129-150-29-79.SFBay.Sun.COM [129.150.29.79]) by mpk-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003))
 with ESMTP id <0IH300A05UAIEV@mpk-mail1.sfbay.sun.com> for
 jdo-dev@db.apache.org; Thu, 26 May 2005 09:11:06 -0700 (PDT)
Date: Thu, 26 May 2005 09:15:59 -0700
From: Michelle Caisse <Michelle.Caisse@Sun.COM>
Subject: Re: tck test status
In-reply-to: <200505261635.32108.andy@jpox.org>
To: jdo-dev@db.apache.org
Message-id: <4295F63F.4010604@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_sX1VjBDUdW8uKGHh12Rn9g)"
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2)
 Gecko/20040803
References: <428D3AD6.3030103@sun.com> <200505261410.40219.andy@jpox.org>
 <4295E9DA.2070600@sun.com> <200505261635.32108.andy@jpox.org>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

--Boundary_(ID_sX1VjBDUdW8uKGHh12Rn9g)
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT

Andy,

Yes, this is a different issue.  Using the <join> fixed the previous 
problem I was running into.

In the TCK, we are starting with pre-defined schemas and mappings from 
the classes to the schemas.  There are other valid schema/mapping sets, 
but we can't just let the vendors autogenerate schema to pass because

(1) We can't test all the mapping metadata if we do that.
(2) Not all implementations will have automatic schema generation.

Apparently there is a gap in the spec around specifying the PK for a 
join table, so this is a tricky case.  We have to find some solution to 
that.

-- Michelle

Andy Jefferson wrote:

>>I've done that, but then JPOX seems to want a primary key in the join
>>table and supplies it, though there is none in the schema or metadata.
>>
>>    [java] [FATAL] tck - Exception during setUp or runtest:
>><javax.jdo.JDODataStoreException: Put request failed : INSERT INTO
>>EMPLOYEE_PHONENO_TYPE (PHONENO,EMPID,ADPT_PK_IDX,"TYPE") VALUES (?,?,?,?)
>>    [java] NestedThrowables:
>>    [java] SQL Exception: 'ADPT_PK_IDX' is not a column in table or VTI
>>'TCKUSER.EMPLOYEE_PHONENO_TYPE'.>javax.jdo.JDODataStoreException: Put
>>request failed : INSERT INTO EMPLOYEE_PHONENO_TYPE
>>(PHONENO,EMPID,ADPT_PK_IDX,"TYPE") VALUES (?,?,?,?)
>>    [java]      at
>>org.jpox.store.rdbms.scostore.NormalMapStore.put(NormalMapStore.java:462)
>>    
>>
>
>Michelle,
>
>This is a different issue to the one before. You previously had a M-N between 
>Employee and Project - and so adding the <join> to the other end should have 
>fixed that, presumably it did.
>
>What is this relationship causing the issue ? I'm guessing a Map in Person of 
><String, String>. It is a perfectly valid thing for an impl to want to put a 
>PK on any table.  It is also a valid thing for an impl to add additional 
>columns where required to allow duplicates etc. Depends on the exact nature 
>of this relation in question. This page
>http://www.jpox.org/docs/1_1/relationships_1_N_map.html
>shows what JPOX currently does for Maps. If you can identify which one you 
>have, then maybe Erik or I can remember why there is an ADPT_PK_IDX column 
>being added in this particular situation.
>
>
>PS. Next nightly build (20050527) will *not* need the use of <join> on both 
>ends of a M-N, so you can have a "mapped-by" on one end and <join> on the 
>other end of the M-N as you had before.
>
>  
>


--Boundary_(ID_sX1VjBDUdW8uKGHh12Rn9g)--