4 ms·
An interesting problem with making a MongoDB GUI is that a key feature of every SQL GUI -- a rich <table> of your data that you can use to see it and play with
by phillco 14y ago
An interesting problem with making a MongoDB GUI is that a key feature of every SQL GUI -- a rich <table> of your data that you can use to see it and play with it -- won't work as well, because MongoDB doesn't have strict table definitions. (Or 'tables' for that matter). Each item in a collection could have completely different fields. So given a big collection of this irregular data, how do you display it compactly? Listing each element in JSON is inefficient.
- ankit_b 14y agoGreat point. This is what we have been discussing internally. One option would be to let folks define an "object" (Read table structure) and display based on that.
- suresk 14y agoI've kicked around some ideas for this problem a while back. I think letting users define a "view" like this is a pretty good approach. I also think a reasonable default is to just pick the the N most popular (where "popular" means defined and non-empty) non-object/collection fields in the root document and display them in a table, then double-clicking or whatever on that row brings up the full document.
- taligent 14y agoEven a simple code folding approach would be fine for showing the JSON.