Ok so pretty much everyone here knows that behind the Datastore API there's BigTable that's storing our data, so obviously we aren't dealing with a relational database. The good thing here is that I understand I can't use the same relational schema design thinking. The bad part is .... what schema design do I use?
Obviously I've been so accustomed to relational thinking ... so now I'm at a point where I want to be able to adopt a design that's naturally suited for Datastore/Bigtable, but I don't know where to start. I see discussion fragments here and there (e.g. http://groups.google.com/group/google-appengine/browse_frm/thread/b5696cc608bf76f9/0a42bf3fb94054c0?lnk=gst&q=Disapointed+by+the+speed+of+the+db+backend+...&fwc=2 ) and the documentation for the Datastore API, but I really haven't found a source where I can fully emerge myself in the *new* thinking. Furthermore, the Datastore API has elements that I imagine are there to ease the transition from the relational mindset (such as GQL and ReferenceProperties) but that also makes it difficult to really adopt the new design model. Those features seem to prohibit new thinking. So with this context in mind, does anyone know of any resources that will help in designing database schemas/models for web applications specifically targeting App Engine/Bigtable (besides Bigtable whitepaper)? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
