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

From: Lachlan Deck (lachlan.dec..mail.com)
Date: Thu May 31 2007 - 02:19:28 EDT

  • Next message: Craig L Russell: "Re: Abstract Entities [Was: Modelling improvements: inheritance + interfacing (Draft)]"

    Hi Craig,

    On 31/05/2007, at 4:13 PM, Craig L Russell wrote:

    > On May 30, 2007, at 8:19 PM, Lachlan Deck wrote:
    >
    >> However, my question remains this: if not defined in a
    >> relationship where does the developer define the delete rules etc?
    >> Or are you suggesting they don't get an option?
    >
    > In an inheritance situation, there is only one instance
    > corresponding to the rows (one row in each table in the hierarchy).
    > I'm suggesting that there is no option. If the instance is deleted,
    > then the row in each table is deleted.

    That's fine when the parent is abstract (i.e., not instantiatable).
    What about when the parent is not abstract and where it is thus
    possible to simply fetch/instantiate the parent entity on its own.
    What happens when the user deletes the parent object in such a
    situation? Should I not get the choice?

    with regards,

    --
    

    Lachlan Deck



    This archive was generated by hypermail 2.0.0 : Thu May 31 2007 - 11:24:14 EDT