Of course you can use id/name to instead of reference property, but you can get some benefit when using reference property.
One is back reference. If a reference to b, b also reference to a, you need store a's key in b and b's key in a. But using reference property, you can automatically get a back reference. Once you need change the relationship, link a and c, you don't need change a, b, c at the same time(maybe a transaction), just change a's reference property to point to c, and everything has been done. 2009/11/29 MajorProgamming <[email protected]>: > I was wondering: isn't using reference properties a waste of space? > Wouldn't it make more sense to store the id (assuming not using > key_name) of the entity. After all, if the Kind is known, one can > easily generate the full key based on that. And with a reference > property it actually stores the _entire_ key (very long!). > > Why? > > -- > > 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.
