Take a look at Contacts.LOOKUP_KEY. Lookup keys are far more stable than contact ids. For example, they are used in contact shortcuts. On Dec 6, 2010 2:22 PM, "Mak" <[email protected]> wrote: > I am interested in your opinions on the best way to keep a robust > reference to a contact starting android 2.0. I have read a lot > regarding this issue but i don't know which technique is advisable and > if there's any new ones. Below are the 3 options i found so far: > > 1- Don't use your own db. Extend the contacts.contract to write your > data > > 2 - Use ContentObserver to keep track of any changes made to the > contacts. This technique would however require your application to be > running > > 3- Store all RAW contact IDs related to a CONTACT_ID in your db and > infer the content of the aggregate contact from all its constituent > RAW contacts > > In my case i need to keep a separate db and i was wondering if there's > any other new technique of keeping the CONTACT_ID current after > aggregations and dis-aggregations.. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
