Whoops. I guess I'm a dumb ass and I forgot to read the docs fully: http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/taskqueue/TaskAlreadyExistsException.html
...oh it's been a long night.... On Mon, Dec 20, 2010 at 11:13 PM, Patrick Twohig <patr...@namazustudios.com>wrote: > Hi, > > I'm using the task queue to write a task that will iterate over all > entities of a certain kind in the datastore. The task needs to perform an > operation on each entity once, so I basically do a two-pass approach. ON > the first pass, I actually iterate the entities enqueueing a separate task > for each entity. Following that, the actual "work" gets executed for each > entity. I'm using named tasks to ensure that each entity is processed in > its own sub-task once. My question is, what happens when I try to enqueue > two separate tasks with the same name to the same queue? Do I end up with > an exception or does it fail silently? And before anybody says anything, > yes, I do know that there's a chance that with named tasks it's possible > that it can actually get enqueued twice. The documentation leads me to > believe that this is extremely rare and for this particular use case a hard > guarantee is not necessary. > > Cheers, > Patrick. > > -- > Patrick H. Twohig. > > Namazu Studios > P.O. Box 34161 > San Diego, CA 92163-4161 > > -- Patrick H. Twohig. Namazu Studios P.O. Box 34161 San Diego, CA 92163-4161 -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
