Yes, that helps. Mainly, you want to make sure the keys for your most frequently used entities are the shortest (see Huffman Encoding) if you will have a large datastore (though, this may be good practice in general).
It is discussed in the Building Scalable Web Apps IO talk from this year: "Building Scalable, Complex Apps on App Engine" http://www.youtube.com/watch?v=AgaL6NGpkB8 Anyway, I highly recommend everyone developing apps on Appengine watch any IO talks from 2008 or 2009 having to do with GAE or Bigtable or other stuff. Google has gone out of its way to explain to people how to make their applications radical.. or fast or scalable or whatever word pleases you. On Nov 4, 9:55 am, Anh Hai Trinh <anh.hai.tr...@gmail.com> wrote: > Since every full entity key includes the name of its model class (and > its parents'), is the following scheme preferable in term of metadata > space usage? > > Instead of > > class MyModelClassWithLongName(db.Model): > ... > > I'd use: > > class MWLN(db.Model): > ... > > MyModelWithLongName = MWLN > > ----aht --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
