Community
Participate
Working Groups
This is a judgement call, but currently the way to establish a bidirectional OneToMany is to use the bidirectional ManyToOne. I found this unintuitive as I, and I think most people, think of a bidirectional relationship between and owning object and an owned object as a OneToMany with a ManyToOne back. As such I'd like to see support for a bidirectional OneToMany in addition to/or replacement of the bidirectional ManyToOne.
I think it should be an addition (not replacement) for the current ManyToOne.
The 3.2 target now represents the Juno release.
Retargeting this bug to the Kepler realease (3.3).
Retargeting this bug to 3.4 release.
Bulk move to Dali 3.5 as Dali 3.4 has shipped.
Deferring from 3.5 to Future target.