Ok, my bad. In the light of day the entity keys are different: The difference was one character, an i changed to a j, probably due to the ID being incremented.
Changing my code to use a key name so that the task does a get before the put to check if the entity already exists. Dale On Mar 25, 12:41 am, Dale <[email protected]> wrote: > Hi > > I insert an entity in to the datastore using a task. The first time > the task ran it successfully put the entity, but the code crashed > after the put (I forgot to include logging.) The task re-ran 7s later, > and did the put again. This time due to a slightly different code path > after the put it didn't need to log, and task completed successfully. > > However, on that kind I have two entities with the exact same key, > just with different ID's. The data of the two entities is the same. > > I thought that it was not possible to have two keys that were the > same. Did I miss something? > > I am using high replication datastore. The entities do not have any > parents. > > Any help would be appreciated. > > Dale -- 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.
