Share your ideas with us
62 results found
-
Explain plan seems to ignore .special or .hint on find queries
I am trying to provide the hint and either atlas is not using the index I am suggesting or the shell is ignoring it when doing an explain. The explain is showing that it is using a different index.
1 vote -
Enhanced static checking in Intellishell
The scripting process in Intellishell would be MUCH faster with static checks that identifiers have a value.
For example the editor does catch the following very, very common mistake;// declaring some variable
const someVar = db.getCollection('someColletction').findOne();
// erroneously referencing some other (undefined) variable since the user misspelled it
print(someVarr);Even worse, the misspelled identifier could have a value stored in the interpreter (from a previous execution) even if it doesn't appear in the current version of the script. This is a problem since the code could actually execute, and dangerously give unexpected results (for example, the user updates documents…
1 vote -
Show collection name on Tab title by default
When open several tabs to edit/view different collections, it's hard to know which tab is for which collection.
I think its good to show current collection name on Tab title by default, to help users recognize.1 vote -
Make fs.files (and fs.chunks) data deletable with a task if the _id is not referenced in any collection
Make fs.files (and fs.chunks) data deletable with a task if the _id is not referenced in any collection and run it every day part of scheduled task within 3T.
1 vote -
Please do not write into the user home directory without explicit permission
Currently 3T writes settings and other things into the user home directory under
.3T,.swtand.cache(on macOS; possibly different on other systems). This clutters the home directory and is therefore generally discouraged.On macOS specifically, Apple user interface guidelines dictate that settings should go into the folder ~/Library/Preferences, and cache files should go into ~/Library/Caches. Similarly, on Linux the generally agreed-on guideline is to adhere to the XDG Base Directory Specification.
3 votes -
Grouping of Tabs based on some name(JIRA ID)
Hi,
On regular basis I spend lot of time on DB for investigating multiple JIRA simultaneously.
Some this when I am working on a JIRA, in mid of investigation i used to get PROD issue which takes highest priority.
The PROD bug and previous JIRA the one I am working may be related same collections(which are around 10-12 collections).
By the time i resolve PROD issue, I end up with opening same collection multiple times with different query results.
I need to go through each collection and its query to make sure which window should be close and which window…1 vote -
1 vote
-
Change Foreground Color of the "Enable Query Assist" Tab
When the dark theme is configured, and you click on the "IntelliShell" button, the "Enable Query Assist" tab name background color turns to a bright light blue that makes almost impossible to read as the letters are white. Please, review the back/foreground colors for these tab and all the others in the shell panel to keep color uniformity when hovering and when selecting those tabs.
1 vote -
Generate Schema to Collection via TASK
TL;DR There is a need for the ability to create tasks that will generate the desired schema documentation with the output being a MongoDB collection that can be used for tracking data improvements over time.
The greatest endeavor we continually face when working with clients on their data cleanup initiatives is the ability for us to report upon the improvements we have made to their data over time. Currently, these improvements can only be measured by a "PowerBI" report that is now aligning more with "their expectations".
We can generate the documentation we need on Schemas and save them in…
1 voteHi there, thanks for this feedback. It will be included in a future discussion for user comments.
-
SQL subqueries
While this has been requested as part of other requests, I wanted to ask for this feature specifically. It would be a game-changer for me.
SELECT * FROM mytable
WHERE foreignKeyColumn in (SELECT _id FROM lookupTable)2 votes -
Export to excel format (additional to csv format)
Using a true excel export format would eliminate problems with floats using a . or a , for digits separations and date format. Where excel-expecting another local date/float format. These stuff is mostly a problem outside the USA (say the rest of the world using different time formats and floating point formatting)
7 votes -
check box to analyze array schema with all positions equally
we use a lot of arrays inside documents. there is no depedency on position to schema, all positions matter equally and are derived from some version of the same object. So it's usually way more important to see schema variation grouping all positions equally and not breaking out [1], [2], [3] etc. so maybe as an option on the schema setup page.
2 votes -
Use proxy settings for IntelliShell
If the database connection has a proxy setup IntelliShell does not use the same proxy and therefore fails to connect.
3 votes -
Add parameters to tasks
It would be great to be able to set parameters on tasks that can be used in the filters, then when you execute or schedule them you would be prompted for the parameter(s)
7 votes -
bring back the simple export for query results
It now takes 20 extra steps to export from a query result and the task cannot be saved. I used to be able to run a script with N queries and then export each tab for analysis with 5 simple steps (and the application remembered the previous selections so most of the clicks were for next). Now all the little changes have to be defined each time and there are so many steps.
I can see how the new wizard can be great for the cases you can save as a task but for the cases you cannot save it…6 votes -
remove ability to scroll mouse wheel over visual query builder
When creating complex queries in the visual query builder there is frequent scrolling required. most mouse pointer devices now have scroll wheels which are critical for big data exploration. Currently your record fields change if you are hovering (not selecting) over your fields in the visual query builder, which changes there values. This is extremely frustrating, and breaks the result. You should only be able to change this value of you have positively selected the object with a left mouse click.
7 votes -
Query builder doesn't respond when some execution is already in progress
Open any collection--> While the data is loading, try typing something on "Query" or "projection" section. It doesn't allow. In fact the background processing is blocking the UI thread. Mongodb Compass has done pretty well in this. Contact me if the issue still not clear.
1 voteThanks a lot for reporting this.
We’ll take a look at this and endeavour to have a fix in an upcoming release of Studio 3T.
-
Copy and Paste shortcuts are inconsistent with Dvorak layout.
On a Mac, and possibly in windows as well (but have no verified), the copy and paste shortcuts are inconsistent. From IntelliShell and other large text areas, Cmd+C/V work as expected. But in the smaller text boxes, such as the Query, Projection, etc input areas, I have to use Cmd+J/K (the physical key locations of C and V in the qwerty layout). This bug has been around since the product was called MongoChef
1 voteThanks a lot for reporting this.
We’ll investigate and seek to make consistent shortcuts available in an upcoming release of Studio 3T.
-
Bring the Update dialog to the front
When I start Studio 3T and there is an update ready, the dialog that tells me that an update is ready always goes behind other windows on my machine. Consequently I end up wasting time waiting for the app to load because I'm thinking it's doing something when it is in-fact waiting for user input.
I'm using Windows 10 and the latest version of Studio 3T.
Can this either not be a modal dialog (i.e. an option on the Studio 3T UI) or a modal dialog that is forced to be the top-most window being displayed. At the moment, it's…
2 votesThanks a lot for pointing this out.
We’ll investigate and endeavour it include a fix in an upcoming release of Studio 3T.
-
Show the current elapsed time when running big aggregations.
It currently only shows the elapsed time when the query is complete.
1 voteThanks a lot for making this suggestion. It’s a nice idea, and would probably apply to any long-running query in Studio 3T.
We’ll investigate and endeavour to include this improvement in an upcoming version of Studio 3T.
- Don't see your idea?