generally, g:id is a surrogate id you can add only during inserts and required for some item-types; whereas atom:id is read-only but required for updates and deletes; if the g:id of an existing item is used during an insert then the existing item's data will be overridden.
item expiration isn't intended to simply nudge a date but rather to keep data fresh and accurate especially for the products item-type. updates replace data of existing items based on atom:id -- so any missing data is an essence a delete of that data; updates should retain statistical data as far as i know. using 'updated' probably didn't work because g:updated is different from atom:updated and atom:updated isn't writable except by google. g:expiration_date can be updated with its proper atom:id see also http://code.google.com/apis/base/starting-out.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" 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-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
