Share your ideas with us
723 results found
-
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 -
Specify a shard key for UI editing
It would be great if there was a way in the UI to specify a required field for updates other than the _id so that it would be possible to update on a sharded DB without using the shell. Specific use case here is Azure CosmosDB which requires a partition key on all collections and that key has to be part of the find clause for updates.
1 vote -
I wish I could increase the font in the top of the query panel.
It's way too small and I basically struggle every day to see the small font. colon vs semicolon is just hard to see.
3 votes -
auto hide all tabs
It would be helpful if you could provide a auto hide feature like the way we have in sql server and and command to show or hide results window below
1 vote -
A web bug reporter/tracker.
A web bug tracker for reporting and following bugs/problems similar to Mongo Jira would be very useful.
I send bugs to support, then I have to continually ping support for a status. A bug I recently reported has gone through two update cycles without being addressed, so I have to hit on support for updates.
1 vote -
Migrate Empty table structure to mongodb
Migrate Empty table structure to MongoDB:
I have a table without data On the SQL server.
I am doing SQL to MongoDB migration using SQL to MongoDB Migration.
But the tables without data is not creating collections in MongoDB.Please assist in how to migrate those types of tables.
1 vote -
Allow the same two collections to be used multiple times in a Compare/Sync task
I have two compare different sets of documents in the same collections based on different match and filtering criteria. Currently I cannot add the same collection pair multiple times to Compare Sync and apply differetn criteria to each.
1 vote -
Automatic threading of _id to collection
In locally stored collection metadata, a field could be configured to be interpreted as an _id of a document in another collection. That way, when a field with such metadata was selected, the resulting pulldown could contain a 'Jump' entry. Selecting jump would open the target collection in a new tab and find that element. It would make referenced documents much quicker to access.
1 vote -
Allow to choose the Protobuf Deserialization
When data is serialized using Protobuf, then Studio 3T may not be useful to get the values which will be in Binary format. If Protobuf serialization is supported, then it would be great to have one tool supporting multiple serialization techiniques.
1 vote -
why should I use delete and shift delete to remove document and element??
Why not just press delete? how should I know?
1 vote -
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 -
Set column width according to data AND title
Currently, double clicking a column border sets the column width to the widest data. If the column title is longer than the data, the text title is clipped.
When double clicking the column border, the width should be set to the widest content, the data OR the column title.
1 vote -
add autosort for collections
90% of the time I want to see what documents were created most recently. I have a "date_created" attribute that I'd like to be able to sort on by default.
Clicking the header in the collection only sorts the documents shown, not all the documents in the collection.
1 vote -
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 -
Extended task scheduling
If I want a task to run more than once per day, I have to clone a separate instance of the task for each scheduled run. This is particularly tedious if I want something to run every 10 minutes, 24/7/365.
Would be MUCH better if I had full cron-like control over the task schedules.
1 vote -
Generate task scripts
Tasks and Scheduler are very handy for prototyping. Would be even better if S3T could generate scripts for executing the tasks in test or production environments, and without requiring S3T to be running on a desktop at the time the scheduled task is to run. (Maybe a command-line S3T, or S3T task-runtime package?)
4 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 -
Debugging of scripts
Possibility to set breakpoints and debug more complex database scripts in the script editor.
1 vote -
redeclaration of const
If you run a script twice in intelli shell, and you use a cons x = 3, you cannot run the script again.
[js] TypeError: redeclaration of const x :
even if you change it to a var afterwards, it still produces that error.
It seems that the context is kept between running scripts?3 votes -
When importing large json files, the error reporting provides a position value for the error which really does not help.
I suggest that at the very least the document number for which the error occurred be provided. Line number or position within document would be very helpful.
1 vote
- Don't see your idea?