Re: Abstract Entities [Was: Modelling improvements: inheritance + interfacing (Draft)]

2007-06-01 Thread Andrus Adamchik
On May 31, 2007, at 9:51 AM, Lachlan Deck wrote: There are numerous uses for these partial instances (if you'd like to call them that) when you want to only fetch the characteristics of the parent, for example, without also having to fault in the data for the subclasses. e.g., if I have a

Re: Abstract Entities [Was: Modelling improvements: inheritance + interfacing (Draft)]

2007-06-01 Thread Andrus Adamchik
IMO, "abstract" is limited to its Java definition, and is of no consequence to the runtime inheritance processing (note that 'resolvingInherited' query property is true by default). So the most important aspect of it is generating a corresponding Java class with an "abstract" keyword, so th

Re: Abstract Entities [Was: Modelling improvements: inheritance + interfacing (Draft)]

2007-06-01 Thread Andrus Adamchik
Hi, Per http://cayenne.apache.org/mailing-lists.html the right email address is "[EMAIL PROTECTED]". Let me know if this still didn't work, and I'll unsubscribe you manually. Andrus On May 31, 2007, at 8:44 AM, srinivas sagar wrote: I have tried to unsubscribe from this list by sending a

Re: vertical inheritance joins

2007-06-01 Thread Andrus Adamchik
This was a long thread, and I may have missed some points already made. Let me try to summarize this discussion and add my comments to it. There are two aspects of the "vertical inheritance relationship": 1. Specifying the join semantics for non-trivial PK-to-PK mapping (such as compound ke

Re: Abstract Entities [Was: Modelling improvements: inheritance + interfacing (Draft)]

2007-06-01 Thread Lachlan Deck
On 01/06/2007, at 6:55 PM, Andrus Adamchik wrote: IMO, "abstract" is limited to its Java definition, and is of no consequence to the runtime inheritance processing (note that 'resolvingInherited' query property is true by default). I was thinking that 'isAbstract' (if true for the parent en

Re: vertical inheritance joins

2007-06-01 Thread Lachlan Deck
On 01/06/2007, at 7:32 PM, Andrus Adamchik wrote: With this in mind we do not need an inheritance ObjRelationship, but we may use a DbRelationship to store join semantics (anybody mentioned that already??). Well the original suggestion I made was for superRelationship="nameOfRelationship" .

Re: Abstract Entities [Was: Modelling improvements: inheritance + interfacing (Draft)]

2007-06-01 Thread Craig L Russell
On Jun 1, 2007, at 2:42 AM, Andrus Adamchik wrote: On May 31, 2007, at 9:51 AM, Lachlan Deck wrote: There are numerous uses for these partial instances (if you'd like to call them that) when you want to only fetch the characteristics of the parent, for example, without also having to faul

Re: Abstract Entities [Was: Modelling improvements: inheritance + interfacing (Draft)]

2007-06-01 Thread Lachlan Deck
Hi there, On 01/06/2007, at 10:50 PM, Craig L Russell wrote: On Jun 1, 2007, at 2:42 AM, Andrus Adamchik wrote: On May 31, 2007, at 9:51 AM, Lachlan Deck wrote: There are numerous uses for these partial instances (if you'd like to call them that) when you want to only fetch the character

Re: [CONF] Apache Cayenne Documentation: Inheritance overview (page created)

2007-06-01 Thread Mike Kienenberger
It may be wrongly named (to our eyes), but that's what Hibernate was calling it. (Some of these may have also come from Toplink as well). If it makes you feel better call it "Hibernate table-per-subclass" and so on. On 5/31/07, Lachlan Deck <[EMAIL PROTECTED]> wrote: On 01/06/2007, at 9:37 AM