Re: EOModeler Flatten relationship bug

From: Pierre Frisch (pierre.frisc..pearway.com)
Date: Mon Jul 17 2006 - 11:26:41 EDT

  • Next message: Pierre Frisch: "Re: Build number"

    I cannot reproduce it with the latest bug so consider it as closed. I
    will do more testing a bit later.

    Thanks

    Pierre

    On 17-Jul-06, at 4:41 PM, Mike Schrag wrote:

    > The cardinality thing is fixed now ... EOEntity can now resolve a
    > keypath down to an IEOAttribute (IEOAttribute resolveKeyPath(String
    > _keyPath)), and relationship isToMany returns the isToMany value of
    > its target if it is a flattened relationship.
    >
    > For the second problem, I haven't seen this (and couldn't reproduce
    > it in mine). Any time you get this error dialog, there should be a
    > corresponding stack trace in the Error Log view. Can you send me
    > the stack trace from that? The bottom exception of that trace has
    > the actual cause of that problem.
    >
    > Oh, and I also set new relationships to default to be class
    > relationships now.
    >
    > ms
    >
    > On Jul 17, 2006, at 6:35 AM, Pierre Frisch wrote:
    >
    >> Hi Mike,
    >>
    >> I have found a few bugs.
    >>
    >> There is a problem with the cardinality of flatten relationship.
    >> The cardinality should be calculated based on the definition of
    >> the relationship at the moment it is not. This quite a bit of work
    >> as we need to explore the definition path to rebuild each
    >> relationship and determine if it is a toMany.
    >>
    >> The other problem is the class property Boolean it is not set by
    >> default as it should be and when I try to set it manually I get an
    >> error:
    >> <Picture 1.png>
    >>
    >> Thanks
    >>
    >> Pierre
    >
    >

    This archive was generated by hypermail 2.0.0 : Mon Jul 17 2006 - 11:26:47 EDT