On May 30, 2007, at 8:04 AM, Lachlan Deck wrote:
I'm not familiar with the embeddable discussion but this is the
idea of DbEntity interfaces:
a) you have a series of DbEntities that are not inherited in any
way but for which you want them to conform to an interface 'A'.
They are
On 30/05/2007, at 7:16 PM, Andrus Adamchik wrote:
What I am concerned about with DbEntity interfaces is that
DbEntities model database tables and there is no interface concept
in DB world. So I still don't understand why we need DbEntity
inheritance? Could you please elaborate or give
Yes, prototype is a much better word, and such change in
terminology is very important for this discussion to go forward, as
interface has a very specific meaning in OO development. Let's
definitely discuss it separately from the inheritance.
Andrus
On May 30, 2007, at 12:32 PM,
Note that we already have open JIRA issues on creating prototypes.
It's just that no one's gotten around to implementing it yet. For
example,
https://issues.apache.org/cayenne/browse/CAY-225
On 5/30/07, Andrus Adamchik [EMAIL PROTECTED] wrote:
Yes, prototype is a much better word, and such
On 30/05/2007, at 7:32 PM, Aristedes Maniatis wrote:
On 30/05/2007, at 7:16 PM, Andrus Adamchik wrote:
What I am concerned about with DbEntity interfaces is that
DbEntities model database tables and there is no interface concept
in DB world. So I still don't understand why we need DbEntity
On 30/05/2007, at 7:32 PM, Aristedes Maniatis wrote:
3. vertical inheritance (where a special ObjRelationship is created
to specify the superclass. There may also need to be a qualifier
like with single table - Lachlan thinks yes, I'm dubious.)
The qualifier is required for vertical
On 30/05/2007, at 7:16 PM, Andrus Adamchik wrote:
On May 30, 2007, at 8:04 AM, Lachlan Deck wrote:
I'm not familiar with the embeddable discussion but this is the
idea of DbEntity interfaces:
a) you have a series of DbEntities that are not inherited in any
way but for which you want them
