1. I can suggest adding new column by double-click *OR* single click on
right arrow. That's probably more intiitive.
2. You might be right, but I can't see what can be done about it - ?
3. So this comes to not allowing sequenced reverse one-to-one relationships?
(A->B->A). I'll do it that way
2008/7/23, Kevin Menard (JIRA) <de..ayenne.apache.org>:
>
>
> [
> https://issues.apache.org/cayenne/browse/CAY-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013#action_13013]
>
>
> Kevin Menard commented on CAY-1077:
> -----------------------------------
>
>
> I've been away from the issue a bit myself and needed a refresher.
>
> 1. I guess you could boil it down to that. I think it's more of an issue
> of there always being multiple columns, even for what should be a toOne
> relationship. I think a double-click could work, but we'd want to make sure
> that's somehow intuitive. I'm not sure it is with a columnar selector,
> unfortunately.
>
> 2. Indeed, the sync button does work well. My issue was more with the ease
> at which a user can break a sync'd connection. Maybe I'm trying to be too
> protective, but being able to convert a toOne to a toMany is simplistic to
> the point of being hazardous, IMHO.
>
> 3. I should have clarified a bit more. Of course toMany could have
> interesting relationships and detecting a static cycle in that case would be
> impossible. But, for toOnes with bi-directional relationships, we can
> detect cycles fairly easily. We should not allow such to be mapped.
>
>
> > ObjRelationship Mapping Dialog Improvements
> > -------------------------------------------
> >
> > Key: CAY-1077
> > URL: https://issues.apache.org/cayenne/browse/CAY-1077
> > Project: Cayenne
> > Issue Type: Improvement
> > Components: CayenneModeler GUI
> > Affects Versions: 3.0
> > Reporter: Andrus Adamchik
> > Assignee: Kevin Menard
> > Fix For: 3.0
> >
> > Attachments: patch-CAY-1077.txt
> >
> >
> > [This is a GSoC 2008 task]
> > The biggest complaint about the ObjRelationship mapping dialog is that it
> is often unclear how it operates, especially to the new users. I.e. empty
> list of DbRelationships is displayed as a white area, not giving any hints
> on what needs to be done to map a relationship. So that's confusing. Same
> thing when you add 1 path component, there is no hint that you can chain
> more path components for the flattened relationship.
> > At the minimum we may just add some hint text ("Select next
> DbRelationship" in grey over the next available dropdown), but ideally we
> should implement a path browser, similar to how the SelectQuery prefetch and
> ordering browsers operate (and similar to how OS X Finder does).
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
This archive was generated by hypermail 2.0.0 : Wed Jul 23 2008 - 16:03:06 EDT