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 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

On Wednesday, September 26, 2012 5:14:36 PM UTC-4, Daniel Wong wrote:
>
> 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
>
> On Wednesday, September 26, 2012 9:28:33 AM UTC-7, Guy Armitage wrote:
>>
>> I fell you pain Jason.
>>
>> +1 big time, at least let us expand the columns if we need to (at worst!)
>>
>> On Wednesday, September 19, 2012 8:21:51 PM UTC+1, Jason Collins wrote:
>>>
>>> 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?
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/4g3Q9JAE-m0J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to