On Feb 6, 3:47 am, Larry <larry.ches...@googlemail.com> wrote: > My question is: what is the most effective and fastest way to handle > these requests while ensuring that no request is lost and no request > creates two VoteRecord objects?
You can use a key_name for your VoteRecord entities which is based on the ID of the user. You can then use Model.get_or_insert() to make sure there's only one VoteRecord entity per user. Another possibility is to set User entities as a parent of VoteRecord entities and use transactions explicitly. --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
