Hi Mark and Jeff, On May 16, 4:03 am, "Mark Murphy" <[email protected]> wrote: > That may work for content providers that pass WHERE clauses straight on to > SQLite.
Awesome - thanks. If I rely on behaviour like this is it going to remain consistent between major releases of android? i.e. will my app at least be fine for 1.5.X? (Do they even drop point releases to phones or is it set in stone/ firmware until the next major version?) On May 16, 8:17 am, Jeff Sharkey <[email protected]> wrote: > If you're looking for a permanent reference to a contact, use a > combination of _SYNC_ACCOUNT and _SYNC_ID, which will uniquely > identify each contact. This also applies to any other provider on the > system that offers syncing, such as Calendar. Looking at the docs for Contacts.People._SYNC_ID it says this will be null if it's never been synced. I guess this would mean contacts stored locally on the phone can't be referenced this way? It also creates an issue if somebody selects a contact which hasn't been synced yet. Any suggestions for something generic that'd cover the first two situations, though ideally all three? Cheers, Alan. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
