Return-Path: 
 <jdo-dev-return-871-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org>
Delivered-To: apmail-db-jdo-dev-archive@www.apache.org
Received: (qmail 95051 invoked from network); 28 Jul 2005 15:04:40 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 28 Jul 2005 15:04:40 -0000
Received: (qmail 83276 invoked by uid 500); 28 Jul 2005 15:04:40 -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 83261 invoked by uid 99); 28 Jul 2005 15:04:40 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2005 08:04:39 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [195.179.68.194] (HELO relay01.ipcare.de) (195.179.68.194)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2005 08:04:32 -0700
Received: from a-212-224-30-66.easynet.de ([212.224.30.66] helo=[172.16.1.19])
	by relay01.ipcare.de with esmtp (Exim 4.43)
	id 1Dy9w2-0007NB-IU
	for jdo-dev@db.apache.org; Thu, 28 Jul 2005 17:04:34 +0200
Message-ID: <42E8F402.5040105@spree.de>
Date: Thu, 28 Jul 2005 17:04:34 +0200
From: Michael Watzek <mwa.tech@spree.de>
Organization: Tech@Spree GmbH
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: jdo-dev@db.apache.org
Subject: ORM metadata questioin
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi Craig,

I have an orm metadata question. Consider the following inheritance mapping:

Classes "Person" and "Employee" have inheritance strategy "new-table". 
Classes "PartTimeEmployee" and "FullTimeEmployee" have inheritance 
strategy "superclass-table".

Is is valid to place the dicriminator column in table "employees"? The 
spec seems to forbid that in chapter 18.10:

"...
In the least-derived class in the hierarchy that is mapped to a table, 
declare the discriminator element with a strategy and column.
..."

If it is valid, can you have a nested <join> element and a nested 
<discriminator> element in the same <inheritance> element? E.g.

         <class name="Employee" table="employees">
             <inheritance strategy="new-table">
                 <join column="PERSONID"/>
                 <discriminator strategy="class-name" column="DISCRIMINATOR"
                     indexed="true"/>
             </inheritance>
             ...
         </class>

Regards,
Michael
-- 
-------------------------------------------------------------------
Michael Watzek                  Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de        Buelowstr. 66
Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
Fax.:  ++49/30/217 520 12       http://www.spree.de/
-------------------------------------------------------------------