Share your ideas with us
720 results found
-
Allow aggregate query export to file on first execution.
In order to export the results of an aggregate query to file I have to run the aggregate pipeline first and then use export to export the current results.
My aggregate takes over an hour to run so it takes twice as long to export to file because the aggregate has to run twice.
I would like to be able to configure the export of the aggregate before running the pipeline so it only has to run once.
2 votes -
Fix the lag in the results view
Scrolling in the "Result" tab in every type of view (Tree, Table or JSON) is Extremely slow and laggy.
This is in my opinion a major downside to Studio 3T, a smoother scroll would make the user experience a lot better.5 votes -
Option to copy table view results as Excel Spreadsheet-ready format (not BSON)
As you marked this idea as 'COMPLETED'
https://3t-io.uservoice.com/forums/265122-share-your-ideas-with-us/suggestions/10528350-copy-paste-to-excelI still think always having to export into .csv file is not so convenient.
Could you please provide an option to copy to clipboard as Excel-ready format (not BSON) for simple Table View results?
2 votes -
Run from command line with specified query
We'd like to add a link from our custom application to view a document (or multiple) it in Studio 3T to edit the JSON etc.
Would be nice if we could run Studio 3T from the command line and specify a connection, database, collection and query.4 votes -
Schema diff tool
You have a Compare tool that compares documents from 2 different collections. The comparison I want is at a higher level than the document. I'd like to get a diff of schemas from 2 different collections. You already have a great Schema tool. I'd like to get its output from 2 different collections and generate a diff between the two. So a schema diff rather than a document diff. I can think of many use cases for this. For example do a schema diff between dev and prod to generate release notes for a new release or comparing dev to…
2 votes -
Bold Monospace font for Query fields and others
We should be able to select font for Query Inputs.
The default is only way better on mac and ubuntu.
Windows ... 😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭
3 votes -
Change the surrounding colors with dark theme
When using the dark theme the editor panels go black with white text.
The rest of the background is white which is very bright and disorienting. The Database window on the left and the top nav things should also go dark to match the theme3 votes -
Add a "find by this _id" field
just add a text field where i can paste an _id and hit enter to query by ObjectId
3 votes -
Support ssh-agent if available
Would it be possible to support ssh-agent if available on a system?
5 votes -
Improve IntelliShell: Add "Duplicate Line"
⌘ + D Duplicate the current line
(Below the existing one. Many development environments have this feature. It would be nice to have it in 3T)
2 votes -
Changing the IntelliShell Default
I generally use the IntelliShell (as opposed to the Collection view); and I've always wondered why the default just:
db.COLLECTION.find({})
I almost alway end up typing db.COLLECTION.find({}).sort({'_id':-1}). I wish I could have this as a default instead!
2 votes -
Use fixed width fonts when showing aggregate pipeline and stages
When we are using the aggregate editor, we are shown a tabbed area (Pipline, Stage 1, Stage 2 ...). In each tab, we are shown a 3 column table with headings of "Stage #", "Operator" and "Specification".
In the Specification column, we are shown the JSON that describes our query / aggregation. However ... that specification entry is in a default font that is not fixed width. This makes it difficult to determine relationships if I am using indenting. This suggestions asks for the consideration of using a fixed width font for those "code" areas.
2 votes -
Lookup between 2 database
lookup между двумя базам.
был бы хорошо если добавили бы возможность делат lookup db1.collection1.aggregate => db2.collection2.aggregate
Lookup between 2 database
It will be good to have ability to lookup between 2 databases like that:
lookup db1.collection1.aggregate => db2.collection2.aggregate
This is possible in SQL like database:
SELECT ...
FROM A.table t1
JOIN B.table2 t2 ON t2.column = t1.colThank you for a great job and your online university program, goog luck !!!
10 votes -
open the collection view directly from search box
Hai, I don't know whether some one raised it or not, but i thought this gone be good one. in search box if we select a collection(say x collection), instead of just focus to that particular collection, directly view the collection(i mean if double click on the collection , entire collection data will be viewed). Sorry for my bad english.
Means, I searched for "x" collection, i selected that collection in the search results. That is just highlighting that collection in the DB. Again i need to double click on that collection to view the data. if you remove that…
3 votes -
Variables in aggregation pipelines
I have a few aggregations saved that I use for reporting. Sometimes multiple stages use the same dates (in my case, but could be anything) and it would be nice to be able to set a variable so I could save my pipeline with variable placeholders and then when I run the aggregation I don't have to update each instance of a date, I would only need to update the variable declaration.
I could do this with nodeJS but I don't want to have to boot up a server to run a report when Studio3T makes everything else so easy
2 votes -
Have option in Aggregate Pipeline Project stage to auto-generate entries for all fields in source data
In the Aggregate Pipeline, when the stage is Project, have an option to auto-generate "field_name : 1" entries for all the fields in the source data.
It's not uncommon for me to want to include all or most of the fields I already have, plus a few calculated fields.
But once you add calculated fields, you have to specify all the other fields you want to pass through, in the form "field_name : 1". Otherwise, all you'll get from this stage is your calculated field(s).
I suggest a button or context menu option to auto-generate "field_name : 1" entries for…
3 votes -
Save unsaved queries and reload them on next start
I tend to have many query tabs open at any given time and if I need to restart (or simply close) Studio 3T, it becomes a chore to save them all. Some are temp queries that do not deserve a permanent file.
Is it possible to add a feature where tabs will simply reopen as they were prior to closing the app? Similar to the experience one gets when restarting Chrome browser.
Thanks!
5 votes -
Ability to group databases into folders like dev/uat/prod/private
Provide ability to group databases into folders. similar way as tortoiseHG workbench does. I can create folders like DEV, UAT, PROD or PRIVATE and drag and drop my database there.
9 votes -
Results to JSON View should use multi-thread processing
Converting results to JSON View is painfully SLOOOOW!
I suggest converting that process to multi-thread to utilize the other 7 idle cores on my machine.1 vote -
Support for networkMessageCompressors in connections
Mongo / mongos / mongod support "networkMessageCompressors" since 3.4 and it would be nice to enable support of this option for connections
https://docs.mongodb.com/master/reference/program/mongo/#cmdoption-networkmessagecompressors
Thanks !
2 votes
- Don't see your idea?