Correction to my previous post: This is possible, as Rafe demonstrated in a separate topic:
http://groups.google.com/group/google-appengine/browse_thread/thread/ae8ab7cb83e5f609?fwc=1 Daniel On Nov 18, 11:58 am, "Daniel O'Brien (Google)" <[EMAIL PROTECTED]> wrote: > You're correct in your concern: At present we don't support the sort > of lazy loading that would enable you to fetch a referenced entity's > key without fetching the actual entity. > > One option is to store the key itself as a separate property. You > could even keep the existing ReferenceProperty if you're interested in > keeping it for convenience, and if you don't mind the redundancy. > > Daniel > > On Nov 18, 8:47 am, jhofmann <[EMAIL PROTECTED]> wrote: > > > I am making an app which will store files (relatively large ones, but > > within the 1MB size limit) in the datastore. To make it possible to > > gain information about the files without downloading them I have > > separated their information into two models: Doc and DocData, where > > Doc contains metadata and DocData contains the file. Doc contains a > > reference property to DocData. > > > I want to get the key from the DocData reference and let the client > > use that to make a second http request that gets only DocData(thus > > avoiding the problem of any one request being too large). But I am > > concerned that the syntax "doc.docdataref.key()" is actually going to > > load DocData to get the key instead of using the reference. Someone > > please clear me up on the best way to ensure that I'm not loading > > DocData unnecessarily. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
