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 inclu
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
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
On Tue, Apr 28, 2009 at 8:13 AM, tommytastic wrote:
>
> 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
