Hi Remember you don't really have a table, trying to relate what happens under the hood in the datastore to a relational model is probably the wrong approach.
> It makes the appengine datastore difficult to use because everything > ends up on one table. How is it more difficult other than including a specific class name in the query if you want one of your specific. T On Apr 26, 12:36 am, Tom Howe <[email protected]> wrote: > I'm trying to take advantage of polymodel inheritance and curious to > get opinion of pro/cons of using a datastore model that is essentially > one big table > > My datastore layout is starting to look like this: > > class BaseModel(polymodel.PolyModel, search.SearchableModel): > created = models.DatetimeProperty(auto_now=True) > updated = models.DateTimeProperty(auto_now_add=True) > tags = ListProperty() > > class Thing(BaseModel): > def somemethod(): > ... > > class SubThing(MyThing): > someattr = Property() > > class SubThing2(Mything): > ... > > class Comment(BaseModel): > .. > > class Image(BaseModel): > ... > > This means in the datastore, I see just one table: BaseModel > The advantage of doing this seems to be that I can search across all > items and generate querysets that contain multiple types of items. > It makes the appengine datastore difficult to use because everything > ends up on one table. > What other pros/cons of using this sort of schema? > Is it going to hurt performance? > > Generally using one big table in a regular database is a bad idea. Is > that the same here? > > Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
