I wouldn't want the item deleted until I had done whatever processing I needed to do with its data to ensure it didn't get lost due to a raised exception or crashed machine.
On Oct 17, 9:18 am, "Ethan Post" <[EMAIL PROTECTED]> wrote: > 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 google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
