> Sorry, I misread your original post. The issue here is that the only
> property theBodyentity has is a TextProperty, which is not indexed.
> It's a known bug (we're working on it!) that entities with no indexed
> properties do not show up in the production Admin Console. Your data
> is there, it
Hi Jesse,
Sorry, I misread your original post. The issue here is that the only
property the Body entity has is a TextProperty, which is not indexed.
It's a known bug (we're working on it!) that entities with no indexed
properties do not show up in the production Admin Console. Your data
is there,
> > It sometimes takes a while for new entity types to be reflected in the Admin
> > Console. Are the entities showing up now?
>
> No, I'm still seeing the same errors in the console. My app ID is
> hogbaytaskpaper.
I'm doing a migration, extracting a big TextProperty from my Document
model into
> It sometimes takes a while for new entity types to be reflected in the Admin
> Console. Are the entities showing up now?
No, I'm still seeing the same errors in the console. My app ID is
hogbaytaskpaper.
Jesse
--~--~-~--~~~---~--~~
You received this message beca
Hi Jesse,
It sometimes takes a while for new entity types to be reflected in the Admin
Console. Are the entities showing up now?
-Nick Johnson
On Tue, Jun 23, 2009 at 8:51 PM, Jesse Grosjean wrote:
>
> > Have you added any Body entities to your datastore? Sometimes I get
> > HTTP 500 errors in
> Have you added any Body entities to your datastore? Sometimes I get
> HTTP 500 errors in the console viewer for models with no existing
> entities.
Yes I've added a lot, and they seem to be working, I just don't see
them in the console. I also have an "Includes ancestors" index that's
serving
Have you added any Body entities to your datastore? Sometimes I get
HTTP 500 errors in the console viewer for models with no existing
entities.
On Jun 23, 1:09 pm, Jesse Grosjean wrote:
> I've just added a new model class to my app that's defined like this:
>
> class Body(db.Model):
> c
