Cimballi a écrit :
Not sure about the original idea, but from my point of view this helps
to know what kind of contact mech is behind the purpose type.
For example, if you have a party and you want to get its primary email
contact mech, you search for PRIMARY_EMAIL and you know you will have
only emails (well, if you didn't mess up everything... :-).
If it was only PRIMARY, it could be any kind of contact mech, you
would then have to go through the list to retrieve the contact mech of
type email.
You right if you want find information from ContactMechPurposeType but
the Type information is also present on ContactMech by contactMechTypeId
and you can find this with entityview
Maybe another solution would be to have hierarchical types, so you
would have PRIMARY and a child PRIMARY_EMAIL, and looking for PRIMARY
would return PRIMARY and PRIMARY_EMAIL.
HTH,
Cimballi
On Mon, Feb 1, 2010 at 4:23 PM, Adam Heath <[email protected]> wrote:
There is currently a PRIMARY_EMAIL, PRIMARY_LOCATION, BILLING_EMAIL,
BILLING_LOCATION, etc. Why can't that just be PRIMARY, BILLING, etc?
--
Nicolas MALIN
Consultant
Tél : 06.17.66.40.06
Site projet : http://www.neogia.org/
-------
Société LibrenBerry
Tél : 02.48.02.56.12
Site : http://www.librenberry.net/
