Schema extensions should in general not affect the sync behavior of
clients that
sync the same base schema. It would be similarly bad to try to add a
new required
property in schema extension.
Let me ask. Why do you think you need a new identity key? Are you
trying to keep
your records from identity matching with any existing record? Or is
there some other
reason?
Bruce
On Dec 7, 2007, at 4:21 AM, Yogesh Potdar wrote:
Hi,
I want to add an identity property to entity "event" in Calendar
schema.
Is this possible by extending the existing calendar schema?
Here is the Context:-
For my sync application, to work on Mac OS X v10.4, I have re-
registered the
copy of Calendar schema with above mentioned change. It worked fine
there.
But in case of Leopard, the sync engine is giving error that those
entities
are already registered previously.
Should I go for the schema extension or is there any other concept
that I
can use?
Thanks,
Yogesh
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Syncservices-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
%(user_optionsurl)s
This email sent to %(user_address)s
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Syncservices-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
%(user_optionsurl)s
