Andy Freeman wrote:
> I'd like to use db.ReferenceProperty in A's definition for its model
> checking and auto-fetch capability, but not if there's any over head
> due to back references.
There's essentially no overhead for back references if you don't use
them. There is a tiny overhead when you define A and the
ReferenceProperty adds the back reference property to the refered to
model. If you're using app caching then this only happens when your
application is first loaded in a server instance. There's no cost on
subsequent requests. The back references aren't real properties so
they don't take any space in the datastore.
Ross Ridge
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
