To Clarify, when I said "it makes the datastore more difficult to use, I mis-wrote that, I meant the datastore *admin*.
It would be nice if google could provide some sort of "view" of the subclass entities within the datastore admin to make polymodel use easier to view. Yes, I noticed that it is indexing the class fields - this seems somewhat unnecessary - maybe google can turn that off? What I was concerned about is if having everything in one table was going to cause performance or contention issues, and from what Nick is saying - its not an issue so that's great ;-). Now, when do we get (proper) search and map-reduce? ;-) On Apr 27, 11:34 am, Nick Johnson <[email protected]> wrote: > Hi Tom, > > If you have a legitimate need for having your models all descend from > the same model, go for it. There is some performance impact, but it's > not due to the size of the 'table'*, but rather because the PolyModel > will generate more index entries, and will require the use of > composite indexes in cases where a simple model may not . > > * Consider that every single entity from evey single app is stored in > a single Bigtable table, and you'll see why the number of entity types > you use has no impact. :) > > -Nick Johnson --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
