You have to read thoroughly how to code for the one-to-many in bigtable implementation. Instead of fluffing all the content in one column, use that column to hold an object which fluffs the given objects into it. (Object of Objects, a list in python, a collection in Java.)
When code, you can say, "my_object.that_list". (After getting the my_object through GQL ) Which will give you no worry over queries per second and the likes. The whole operation would be atomic, as we should group the objects in subject with 'parent-child' concepts. But Phil, You may have to forget RDBMS if you wish to use Bigtable and vice-versa. -- 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.
