This was a bug in 2.1. Lookup key was based on the contact name for unsynced contacts, which created the problem you are describing. As of 2.2 we use raw contact ids instead. In both cases we use stable server-side ids for synced contacts. On Nov 29, 2010 11:01 PM, "LSDsl" <gls...@gmail.com> wrote: > Hi. > > Misunderstand with this (getLookupUri(contactId, lookupKey)). > > I store id and lookup in my application. > > After resave contact (change name for example) lookup also changes > (but ID not change) I cannot select contact from DB using > getLookupUri(contactId, lookupKey). Why? In docs "When both IDs are > present in the URI, the system will try to use the long ID first. That > is a very quick query. If the contact is not found, or if the one that > is found has the wrong lookup key, the content provider will parse the > lookup key and track down the constituent raw contacts.". So long ID > is correct in my situation. So can somebody clarify this situation and > say how what information I must store to 100% select contact in future? > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
