Properties Elided

370 views
Skip to first unread message

Jason Collins

unread,
Sep 19, 2012, 3:21:51 PM9/19/12
to google-a...@googlegroups.com
Entities with large number of attributes now do not show all attributes in the Datastore Viewer (unless you drill in), leaving only a "Properties Elided" column. I'm guessing that I can see particular columns by issuing a projection query, but this assumes that I have an appropriate index in place beforehand.

This has pretty severe impact to the usefulness of the Datastore Viewer as a general-purpose operations tool.

Any particular reason this was done? Any possibility of reverting it?

Kesava Neeli

unread,
Sep 19, 2012, 6:44:53 PM9/19/12
to google-a...@googlegroups.com
I totally agree. This seems something new today and now DataViewer tool is not useful at all now. Is it possible to revert this feature back?

Carl S

unread,
Sep 19, 2012, 7:12:54 PM9/19/12
to google-a...@googlegroups.com
This is causing me problems as well. I can no longer quickly scroll through the rows and compare property values.  I run too many different types of adhoc queries to add indices for them all. 

Marcel Manz

unread,
Sep 20, 2012, 7:29:45 AM9/20/12
to google-a...@googlegroups.com
+1

The Datastore Viewer should always show all properties (or at least have some 'Show all' functionality).

Guy Armitage

unread,
Sep 26, 2012, 12:28:33 PM9/26/12
to google-a...@googlegroups.com
I fell you pain Jason.

+1 big time, at least let us expand the columns if we need to (at worst!)

Daniel Wong

unread,
Sep 26, 2012, 5:14:36 PM9/26/12
to google-a...@googlegroups.com
Hey ya'll,

I'm the engineer who implemented this feature. Some background information that might explain why we did this: Some people have entities with huge numbers of columns. Trying to display the table for those would hurt their browsers. Here's the original bug: http://code.google.com/p/googleappengine/issues/detail?id=937

One way we could address this would be to raise the limit. Obviously, my original guess at what a "reasonable" number would be was wrong :P. Therefore, I'd like to get a better idea of how ya'll are using Datastore viewer, so that we can figure out a more appropriate solution. Would raising the limit work for you? Roughly how many columns would you like to be able to see?

I also figured that if you really wanted to see that many columns columns, then you'd just look at individual entities (by clicking the link the first column). Clearly, that doesn't work for you. Is this mainly because you can't ad hoc projection queries?

Anyway, let's carry on the discussion in the issue report. I just wanted to send this out, in case people aren't subscribed to that already.

Daniel

Daniel Wong

unread,
Oct 2, 2012, 8:34:10 PM10/2/12
to google-a...@googlegroups.com
Thanks for the suggestions. Let's carry on this discussion in the bug please :)

On Saturday, September 29, 2012 3:52:19 PM UTC-7, John Thomas wrote:
Hi Daniel,

Why not allow the user to configure the number of columns to display and use your default number as a starting point. Better yet, it would be great if you offered true CRUD functionality within the tool, at a minimum update would be most helpful.

You can already do this in Datastore Viewer: just click on the link in the first cell of any row.
 
You could show your specified columns and if the user wants to take a more detailed view of the information, allow them to click into the individual row. Then you could scroll the columns down and remove the worry about someone blowing up the browser. 

Thanks,

John
Reply all
Reply to author
Forward
0 new messages