4 results found

1. Execute Raw query with query editor

   Currently there is no query editor for executing raw queries, like for batch update and batch delete. Consider to add a query editor.

   18 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  6 comments  ·  Queries  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. mongosh should be its own tab at the top with output options

   I hate how mongosh is at the bottom. It makes it rather hard to see the results as it involves lots of scrolling, I end up having to write a js file and using mongosh in the terminal.
   It would be good if it was it's own tab at the top and give options to view the output differently.
   The best example I can give is how the robo3t does it. When the data can't be viewed as a tree or table, it just outputs it in text mode.

   Something like this is super handy for developers and makes it easier to do things like write an aggregate query that we can directly copy to/from an actual application. While the aggregate feature in compass is ok, it's not an exact match on how we would write it in code.

   I hate how mongosh is at the bottom. It makes it rather hard to see the results as it involves lots of scrolling, I end up having to write a js file and using mongosh in the terminal.
   It would be good if it was it's own tab at the top and give options to view the output differently.
   The best example I can give is how the robo3t does it. When the data can't be viewed as a tree or table, it just outputs it in text mode.

   Something like this is super handy for developers and makes it… more

   •  

   •  

   •  

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. cross cluster lookup (kind of)

   Hi,
   This is more of an add-on request for the aggregate().

   Lets say we have two clusters , second clusters is derived from first cluster ( i-e some of the object ids in second cluster exist only in first cluster ).

   Now I want to do a lookup for the id in the first cluster from the second cluster , which is not possible.

   So , can we have another optional parameter in the aggregate function which allows us to pass the documents , over which we can apply the required stages ( i-e after using find() on cluster 2 , I will pass the result into an aggregate() call for cluster 1 ).

   example query ->
   db1 points to cluster1
   db2 point to cluster2.

   I am working on Node.js -
   let result=[];
   let response = await db2.find().forEach(item=>{
   result.push(item);
   });

   let lookupResponse = await db1.aggregate([<stages>],{},result);

   Here in the second query , the documents in which the aggregate stages should work
   is the documents present in the variable 'result'.

   I hope I was able to explain my idea.
   It would really help if this is added in the next update.

   Thanks,
   Dushyant.

   Hi,
   This is more of an add-on request for the aggregate().

   Lets say we have two clusters , second clusters is derived from first cluster ( i-e some of the object ids in second cluster exist only in first cluster ).

   Now I want to do a lookup for the id in the first cluster from the second cluster , which is not possible.

   So , can we have another optional parameter in the aggregate function which allows us to pass the documents , over which we can apply the required stages ( i-e after using find() on cluster 2… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  1 comment  ·  Aggregation pipeline builder  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Display Documents within a Frame

   When clicking on a large collection (or running a long-running filter), the Documents are loaded within the main window and prevents the users from performing any other operation. By displaying data within a subframe (like for the aggregation pipeline builder), users can continue to work without waiting for the documents to load.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close