And datastore_oject.user.property is maybe even more CPU costly than datastore_oject1.datastore_oject2.property, or vice versa.
On Nov 18, 11:54 pm, Anders <[EMAIL PROTECTED]> wrote: > It's very powerful to be able to do things like profile.user.email but > as you say such call will cause an extra datastore query (unless > already in memory). I have changed a part in my code which is called > frequently and replaced message.account.X with message.X which > requires duplication of X to be stored but which significantly > improves speed/CPU cost performance. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
