I've been reading and googling and searching... but not sure what the
latest, up-to-date information is on this:

in GAE "parents" and "references" are two different things.  when you
create an object in GAE you can, on insert, assign the "parent"... and
this puts the new object into the parents "entity group"... which lets
you:
 - use those objects within transactions in the entity group
 - do a query on an object and specify an "ancestor" (which can be
many many levels up the heirarchy, since the gae "key" actually
contains a composite of its entire entity group path, I think)

when it comes to transactions, I saw a few discussions that said we
can just use the native GAE transaction methods in order to run
transactions... but that doesn't really help unless we can assign
parents to our objects (thus creating these "entity groups").  I also
saw some discussions about implementing this feature of "parents"...
but I can't figure out if it exists yet.

I would really like to be able to use transactions and also do "has
ancestor" queries... but I think there's going to end up being a
disconnect on what is possible in both the the "big table" world and
the "SQL" world... making it difficult to make a single DAL be all
things


HOPEFULLY what I just wrote makes sense... I could very well be
completely confused and would love any feedback to help straighten me
out :)

Thank you,
-Nick Franceschina

Reply via email to