I have a strong background in RDBMS and java, but I am new to datastores like appengine's datastore.
I'm currently working through the OReilly Programming Google App Engine book and am focusing on the python implementation. While the book gives a lot of good theory, it doesn't have much info on data model design - particularly around designing for transactions. Coming from the java world, using transactions was easy and very necessary for complex apps. However, I can't work out if a relatively complex app could be done with datastore because of the entity group constraints for transactions. Is there any documentation recommendations on data model design for appengine datastore? In particular, how to design for best use of transactions. Many thanks in advance, Chris -- 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.
