bump
Also, the invoice entity seems to do this (although it has a join table in InvoiceRole) by having partyIdFrom and partyId. Should these models be normalized by exclusively using *Role entities to describe relationships to parties? I know it's quite a bit of work and greatly breaks backwards compatibility (although a simple script could be written). Should this be a Jira issue or is there specific reasoning behind the approach taken?
===========Chris Howe wrote:
Why is it that the PaymentMethod entity has a field partyId instead of using a join table between Party and PaymentMethod? It seems limiting to do it this way. I realize that it's easier to do it this way and accounts for 80+% of transactions, but it doesn't follow the versatility that the rest of OFBiz does. For instance, for a credit card you can have several roles that people can be for the same credit card. You have cardholder, authorized user, etc.
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Locked
