Hi Ernesto, There will be nearly no difference in performance between the fetching by key_name and vs a ReferenceProperty. The only performance difference is that key_name will be converted to a key before the fetch, so any difference would be *very* small. The key_name will use less space to store, since it does not include the app-id, namespace, or kind name (keys include all of those things).
Robert On Tue, Jan 18, 2011 at 10:48, Ernesto Karim Oltra <[email protected]> wrote: > Actually I'm using key_names intensively in my app, instead of using > ReferenceProperty. I store them in StringProperty when indexes needed, > and TextProperty otherwise; so I am not worried about indexes. My > handlers works with them in URLs, example: > > /profiles/[key name of the account]/edit > /downloads/[key name of the download] > ... > > And I use it when listing downloads for example, not need to query for > the data, only using the key_name to build URLs. > > So I'm wondering if using ReferenceProperty would have better > performance in general. The alternative could be using the whole key > (ag....) or using the key_name of the Key object to build URLs and > render them. > > Which of both ways it's better for perfomance? > > -- > 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. > > -- 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.
