A common task (queueing) is "fetchitem...delete the item once it has been
fetched". Right now that requires a get/fetch and a call to db.delete at
some point. It would be nice if there was a particular attribute that could
be set in the get which would automatically delete the item once it has been
fetched. Google could figure out the most efficient mechanism for doing this
on the backend and we end up saving mcycles by not having to call the delete
for this type of db request.

Stupid? Not stupid? Would anyone else like this feature?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" 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-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to