Hi,

Unfortunately, the updated element is always the Unix epoch.

http://code.google.com/apis/apps/gdata_provisioning_api_v2.0_reference.html#google_apps_tag_atom:updated

-alex

On Jan 23, 1:07 am, Yochan <[EMAIL PROTECTED]> wrote:
> What I am trying to do is to put google gear layer to google apps.
> However, to do sync. from google apps to local databse, we need to
> know which record being added after the last sync. One more issue is
> that there is no way to query the data based on updated date. Does
> anyone has experience on this one? Please advice.
>
> In addition to that, I am trying to figure out what is
> <ns0:updated>1970-01-01T00:00:00.000Z</ns0:updated>
> being used for. If that is to indicate the date of the record being
> updated, it is not accurate.
>
> <ns0:entry>
> <ns0:category scheme="http://schemas.google.com/g/2005#kind";
> term="http://schemas.google.com/apps/2006#emailList.recipient"; />
> <ns0:id>https://www.google.com:443/a/feeds/sadaweb.com/emailList/2.0/
> acer/recipient/888010348%40sadaweb.com</ns0:id>
> <ns0:updated>1970-01-01T00:00:00.000Z</ns0:updated>
> <ns1:who email="[EMAIL PROTECTED]" rel="http://schemas.google.com/
> apps/2006#emailList.recipient" xmlns:ns1="http://schemas.google.com/g/
> 2005" />
> <ns0:title type="text">[EMAIL PROTECTED]</ns0:title>
> <ns0:link href="https://www.google.com:443/a/feeds/sadaweb.com/
> emailList/2.0/acer/recipient/888010348%40sadaweb.com" rel="self"
> type="application/atom+xml" />
> <ns0:link href="https://www.google.com:443/a/feeds/sadaweb.com/
> emailList/2.0/acer/recipient/888010348%40sadaweb.com" rel="edit"
> type="application/atom+xml" />
> </ns0:entry>
>
> Thank you in advance!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Apps 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://groups.google.com/group/google-apps-apis?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to