On 09/10/13 19:15 +0200, Albert Cervera i Areny wrote: > It has come up several times the need of a party_relationship module > that allows to relate one party to another. > > I've just created a blueprint for it. Your comments will be very welcomed. > > > [1] https://code.google.com/p/tryton/wiki/PartyRelationship
Some remarks:
- I will keep the module name party_relationship but name the
models: party.relation.type, party.relation.
- I don't like the xx_related Functon fields. I think the problem
could be fixed by using a Model with a table_query using a UNION
like:
SELECT id, from, to, type FROM party_relation
UNION
SELECT -id AS 'id', to AS 'from, from AS 'to', reverse_type AS
'type'
FROM party_relation
rem: -id is perhaps not the best idea.
reverse_type could come from a join on party_relation_type
- I will add a start_date and end_date on party.relation with an
active Function field that deactivate the relation if current is
out of the limit.
- I'm wondering if party.relation.type should not simply have an
option link to the reverse party.relation.type
A question:
- I don't understand the "embedded party.relationship" view.
--
Cédric Krier
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/
pgpDlyWFyIegW.pgp
Description: PGP signature
