Share your ideas with us
712 results found
-
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 -
Add option to create an updatescript on target server in "Data compare and sync"
First: the Compare function is fantastic it save us already a lot of time.
When comparing databases you can sync the target database with the changes found.
It would be nice to have Studio 3T generate a mongo update script which would do the same as if you had clicked on the "Sync" button.
This way it would easy to generate update scripts for static content.
(Like the "SQL Data Compare" from Redgate)2 votes -
Throttling data imports
We use CosmosDB and we would like to throttle our imports from Studio 3T so that we don't exceed our Max RU/s for our collections (resulting in a 429).
Ideally we could set a throttle rate on our imports that would have a specified amount of time between each document import or max number of imports per second etc.
If there's a way of achieving this already then that would be fantastic!
2 votes -
Be able to work in two+ JSON editor windows simultaneously
Currently it is only possible to open a single editor on one document, or to view one document and edit another, but it is not possible to copy json from the viewer window to the editor.
It would be incredibly useful to be able to work with 2+ editor/viewer windows at the same time.
Currently we must copy a document into another editor, like VSCode, to be able to copy sections into a Studio3T editor window or to work on two or more documents at the same time.
2 votes -
SQL - Mongo Migration Task export
Having a migration task mapping in a computer with studio 3T is great until the owner leaves on vacation or the computer fails. When critical company's commitments rely on that migration task mapping then it must be possible to export and import it into a different studio 3T license.
2 votes -
Mac OS Big Sur Support
Support MacOS 11
2 votes -
Ability to maintain a query templates for most frequently executed
Provide me a feature to add most frequently used queries to be stored in memory so that whenever I need to pull out that query from memory, I will use shortcut keys to retrieve quickly.
This will avoid copy pasting from external sources in to studio3t editor.2 votes -
allow me to use HOME and END keys in the result panel
While I am going through each field if I would like to return back to first field I want to use home key like wise if I want to jump to end of the columns I would like to use End key.
2 votes -
Reverse the order shown by default
When you show raw records for a collection, the order is arbitrary. From my experience with RockMongo, I've learned how valuable it is (and what a time-saver) if you simply display the records, by default, in reverse natural order (i.e., {$sort: {_id: -1}}). See the last one added right at the top is really convenient a lot of the time.
2 votes -
Export/Import bookmarks
Enable exporting and importing bookmarks so that they can be shared across teams.
2 votes -
Support Array.prototype.flatMap() in IntelliShell
Upgrade the level of JS support in IntelliShell to support current/modern JS functions (such as flatMap() and others).
2 votes -
Client Side Encryption within Studio 3T
I would love to have "Client Side Encryption" in Studio 3T so that I can work with my DBs/Collections data with access to my real data even if they have been "written" from another client like pymongo as an example. Non-authorized people will only be able to work with my DBs/Collection viewing only encrypted data, not real ones, within Studio 3T.
2 votes -
Add aggregation stage templates
Add the ability to change the default text of each aggregation stage (and reset to the built-in one).
I would like to be able to, for example, change the default $lookup text so that the string values don't contain spaces (e.g. localField: "fieldfromtheinputdocuments" instead of localField: "<field from the input documents>") so that I can double click to select the entire content of the string, instead of having to delete by hand.
I think that creating templates, instead of just changing the $lookup default, might be a more powerful option.
2 votes -
Print statements are shown only when the whole script is complete
For long running scripts it would be very useful to show print statements during the execution of the script.
Currently, the're shown only when script runs to completion.
Or, maybe, add an ability to report textual progress on the progress bar2 votes -
Editable Query Code view; populate Visual Query Builder from manually-entered queries
If I start writing a query manually in the QBE fields (Query, Projection, Sort, Skip, Limit), I lose those entries if I open Visual Query Builder and start to add query parameters.
Would be awesome if I could switch freely between QBE, Visual Query Builder, and an editable Query Code view, with my query preserved across the three input methods.
2 votes -
Exporting/importing schema (empty collections, validators, indexes, etc.)
During prototyping, I create various collections and incrementally add validators and indexes and partial indexes (unique if not null). It would be great if S3T could generate scripts that I could use to build-out the MDB instance in test and production environments.
Currently I am opening each Index and then copying the JSON and pasting it into a file. But doing that for each index or validator is tedious. Please at least provide a way for me to view/copy ALL of the JSONs at once, or better yet, provide a way to get those with scripted wrappers that I can…
2 votes -
Add preference for default collection view when opening a new collection tab
Situation: You are looking at a small collection of very small JSON documents so you select JSON View. You then need to open a new collection. However, this is a is giant collection with huge JSON documents (multiple arrays of subdocuments). It's so big it can take up to 30 seconds to render and or crash Studio3T altogether. But you can't stop the operation. So just have to wait. What would fix this is an option for default collection view when opening a new collection. I would just set that to Tree View and this situation would happen anymore.
2 votes -
Allow sorting a table view of an array by any element
Currently when I drill down through a document into an array field, clicking the headers implies that the table is now sorted by that element, but in fact it looks to be sorted by the entire array field (basically array[0] is sorted instead).
2 votes -
Open Connections in Tabbed View
Left Panel which displays all the Open Database Connections, should allow Tabbed View instead of scrolling up and down to different servers.
2 votes -
Open selected doc in dialog in Current Operations tab
Currently in current operations you can not easily select a single doc to see it full in Json.
2 votes
- Don't see your idea?