Not to uproot an old thread, but I am experiencing the same behavior and did not expect to.
Julian - Can you help me understand why this is intentional? If I'm thinking about this right, you would be able to retain that use case that you mentioned if the updated timestamp represented the last time this element was *modified*. In fact, if the updated field for a given element always equals time.now(), queries based on updated_min should not work as you described (because updated_min will always be in the past, which will invariably be less than time.now(), all entries will be returned). Any thoughts on how we can get a modified timestamp using the latest APIs? -- You received this message because you are subscribed to the Google Groups "Google Contacts, Shared Contacts and User Profiles APIs" 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://code.google.com/apis/contacts/community/forum.html
