the PartyAttribute entity has partyId and attrName as
the only Primary Keys. Shouldn't the attribute value
also be part of the primary key? My immediate use of
this entity is a unique identification number, which
the current setup is fine. However, if someone were
to use it for something like hobbies, a person may
have multiple hobbies and therefore need the attrValue
as part of the primary key, unless there's a better
place to store this kind of information
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Locked
