On Sep 16, 2:05 am, Bill <[EMAIL PROTECTED]> wrote: > But in all other cases we go with > ListProperty(db.Key) on the side of the relationship that'll have the > smaller list. Except when you expect big lists on both sides of the > relationship. ... > In this case, you have to go to a separate join Kind because the total > number of indexed property values for a single entity is capped at > 5000, and our worst-case Person exceeds the cap without considering > any other property besides name. Right? So we go to:
right. unfortunate, but true. this is one of the main reasons that implementing pub/sub and activity streams on the app engine datastore aren't as easy as they could be. we hope to improve on this eventually. > > finally, transactions shouldn't add a prohibitive amount of overhead. > > in many cases, doing a number of writes in a transaction can actually > > be (a little) faster than doing them outside of a transaction. are you > > seeing a noticeable slowdown with transactions, compared to without? > > There is a large slowdown on the local dev server. I'll have some true. after i replied, i realized you were probably talking about the dev server. i might actually be able to remove that performance hit. i'll take a look tomorrow. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
