And I would add modeling your business because of the UI is not a good sign,
even with D2W (except implementing userPresentableDescription)
Philippe
-
http://twitter.com/prabier
Sent from my iPhone
On 04 Mar 2014, at 19:57, Chuck Hill ch...@global-village.net wrote:
Yikes!
So, if I’m reading this right, you have a class property of “classe()” and
*also* a flattened class property of “lycée()” and you made the (Model) change
to make creating the UI (View) more convenient. Is that right?
If so, you are asking for all kinds of trouble.
Have you verified
On 2014-03-04, 10:17 AM, David Avendasora wrote:
Yikes!
So, if I’m reading this right, you have a class property of “classe()” and
*also* a flattened class property of “lycée()” and you made the (Model) change
to make creating the UI (View) more convenient. Is that right?
If so, you are
On Sun, 02 Mar 2014 16:05:26 +0100
Jean Pierre Malrieu jp.malr...@free.fr wrote:
Actually I think I solved the problem by using the relationship
keypath in the qualifier:
if ( cd.toOneRelationshipKeys().contains(sv1)) {
EORelationship relation1 = entity.relationshipNamed(sv1);
Hi,I am trying to make a flattened to-one relationship (Enqueteur - Lycée instead of Enqueteur - Classe - Lycée) . Using Entity Modeller I navigate down the relation in the outline view then click the flatten button.Below is what I get in Entity Modeller:My first problem is that Entity Modeller
I don’t understand why you try to flatten a to-one relationship. You can
flatten an attribute or a many2many relationship.
Creating a many2many relationship is pretty straightforward: when you create a
relationship between 2 entities, you choose to many on both sides, give a name
to the join
Actually I think I solved the problem by using the relationship keypath in the
qualifier:
if ( cd.toOneRelationshipKeys().contains(sv1)) {
EORelationship relation1 = entity.relationshipNamed(sv1);
v1Qual= new EOKeyValueQualifier(relation1.relationshipPath(),
