In the Aggregation editor it shows Stage 1 to Stage n.
I have an aggregation pipeline consisting of 13 stages (and more are coming). Navigating back en forth is trail and error, or I need to open the Pipeline overview tab.
Why not add the filter type ($match, $addFields, $group, $project etc) IN the tab? Makes navigating much more intuitive.
Great product, loving it!1 vote
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.1 vote
Suppose I have a collection named 'group'. Currently, I am unable to execute a SQL query on this collection as this is a reserved keyword in SQL and, though, manipulations like using ['group'] in SQL query don't throw any error, no result is fetched either1 vote
Hi, we’ve created a ticket for this.
Meanwhile, we can help you to continue your work.
for that particular case, the following sql query should work:
Current release does not have the $merge stage in pipeline combobox.
It would be nice to have it and a mock-up set, like in $lookup8 votes
It would be better if we can copy filters from query build and paste in another tab. As of now we have copy feature, its better to have paste also4 votes
Thanks a lot for suggesting this. We plan to introduce this in an upcoming release of Studio 3T, currently scheduled for 2019.4.
When editing a document as JSON (ctrl+J), it is a modal window, and we can't do anything else on mongo while this window is open.
Moving to an another document to make some copy/paste, or view data on other documents while editing the first one will be great.9 votes
I don't think maybe when you upgraded your SSL as referenced in this post (https://studio3t.com/whats-new/ssl-protocol-security-upgrade/) you didn't catch all the edges.
I can't get newer versions of 3t client to connect to a replica set via x.509. Even with "allow invalid hostnames" checked. The "discovered" entries for the replica set are contained in the SAN part of the cert presented by each node. Mongo v3.4, same URI and certs connect just fine with older MongoChef 3.6. Happy to send along the certs and connection uri.1 vote
Hi Anon, would you be able to send an email to our support AT Studio3t.com address so that we can look into this further for you? Are you still encountering the same issue? Let us know!
- Don't see your idea?