Compass
41 results found
-
New query from text
It would great to have a feature that allows importing a query from text in compass similar to the aggregation pipeline from text feature. Currently if someone has a long multiline find query which includes filter, project, sort methods then the user needs to copy each of the query segments separately and paste them into designated lines in the expanded query options view.
Importing queries from text would improve support team's efficiency that utilise the compass when trying to analyse application queries manually.2 votes -
Make it easier to search by _id
More then half of my queries in Compass is searching by id. Each time I have to add both curly brackets, then type 'id:' then 'Obj', select ObjectId from autocomplete and paste id.
I propose to add 'id' field in OPTIONS, where I could just paste _id string to fire mongoose-like 'findById'2 votes -
Include curly brackets by default in query bar
By default, the query editor is blank. In order to write a query, curly brackets must be added {query: "here"} in order to make a query.
Event the suggestion for writing a query recommends adding curly brackets. (see suggested.png)
If there is a use case where users may want the query bar to remain blank (how it is now), I recommend adding a setting to put in curly brackets by default. Having to add curly brackets every time I want to create and run a query is tedious and counterproductive.
2 votes -
Filter By Hexadecimal
When filtering by number, it would be nice to be able to filter by Hex (Base16) and Binary (Base2) values (ie. { field: 0x12345678 } or { field: 0b10101010 }.
2 votes -
Kill switch for Aggregation Pipeline queries
This would be useful for working with big collections(10 mil+).
When i define aggregation pipeline in Compass, and increase timeout to some high value(because it's big collection so the pipeline can easily run for minutes and let it run, and than while it's running i change some of the stages to something else - due to that intentionally big timeout, i have to now wait before the first query ends, and then try to run the new one.
A kill switch, either manual or automatic on stage change would help with this
2 votes -
Sneak peek to Ref ID's Data from the document itself
When I query for a given document/s in compass it usually contains several ID's that are a reference to other collection.
In some of the cases I need to continue exploring the data on the Ref ID.
It would be nice if I could hover over a give Ref ID and get a sneak peek using hovering scrollable menu (maybe) to the related document.
Even if it has to perform a search and it will take a second to load it's preferable the manually opening another tab, writing the query just to find out a "name" property.
1 vote -
Support for Binary.createFromHexString in filter
It should be possible to create Binary objects from hex in the filter, like it is supported in the mongo shell already.
So far Binary objects can only be created from base64, so a manual conversion from hex to base64 is required.
Such as: {field: Binary.createFromHexString("0123456789abcdef")}
1 vote -
Disable the cache feature from Compass
Every time I click some on some collection, I don't receive the actual data from the database but the cached data. In my opinion, that should not be like that, because that makes me clicking constantly on the refresh button.
If I click a collection then I want the latest and updated data from the database.
One example:
- I open the Compass GUI tool and I click on some collection to see its data.
- I switch to the application that is doing things and executing actions in the database using their own link.
- I switch to Compass,…1 vote -
Optional ID search fallback for ObjectID
If I search { _id: 'd7hw803h2ihdf3h97298dh3' } and the query returns nothing, I should have the option to re-query but with this instead: { _id: ObjectId('d7hw803h2ihdf3h97298dh3') } and there should be a toggle switch to automatically do this re-querying when there's an empty result.
There's no reason not to have this, it's very easy to implement, and it would be some nice quality of life.
1 vote -
Global search query filter
Use case: When we work on Mutli tenant-based system, we have Account Id is common in all collections. When we search multiple collections needs to add filter accounted in every search.
Feature: If we have global filter, we can add common filters and easily search in every collections.1 vote -
Filtering option for Nested objects
actually, as per now it's difficult to handle {column. Fieldname: value}, by using like {column _fieldname: value} it's better to handle in c# with the help of LINQ.
1 vote -
1 vote
-
Evalute numbers as 64bit instead of 53bit of JavaScript
Compass seems to evalute everything with JS, so if you enter {um:-2583493467308876869} it will treat the number as -2583493467308877000 and of course won't find what I'm looking for.
So the fix is to use {um:NumberLong('-2583493467308876869')}, which is a bit painful to type, and even if I do that, the Query History still saves {um: -2583493467308877000}, so basically it's broken ...
1 vote -
Remove the Insight badge blocking the view to my query
There is a insight badge that does not merit that location(see attachment), and stands on the way to modify the queries.
1 vote -
RANDOM VALUES USING THE OBJECTID
Hi,
This is the basic suggestion from my side.we have a unique "_id" in each document while inserting the data can we make any changes in your code for example in our company we have one scenario while working on the aggregation query they need auto-generated value in numbers so it is not possible in the MongoDB.
so I thought we can do that thing based on the _id. because we have a unique field then i converted the _id to string and separated the numbers and alphabetic separately but we don't have unique values the after separating the numbers…
1 vote -
Changes in the objectID which is unique.1
Hi,
This is the basic suggestion from my side.we have a unique "_id" in each document while inserting the data can we make any changes in your code for example in our company we have one scenario while working on the aggregation query they need auto-generated value in numbers so it is not possible in the MongoDB.
so I thought we can do that thing based on the _id. because we have a unique field then i converted the _id to string and separated the numbers and alphabetic separately but we don't have unique values the after separating the numbers…
1 vote -
Query console like the one in Datagrip
We need a query console like the one in the Datagrip IDE from JetBrains so that we can make any query as well as add comments or saving all these queries in the MongoDB Compass
1 vote -
Explain Plan and query to work on all valid queries -- if an official driver works the Compass should be able to help debugging
Mongo Compass Explain Plan cannot work on queries which are using common Java available syntax. Having no way to use Explain Plan on valid queries, without modifying the query, should be a feature.
{ "_id" : { "$in": [{ "$binary" : "6Uk1UVZWl+krPObxzA3wtg==", "$type" : "03" },{ "$binary" : "60Xp1sJ9nMiT6cPy3GA1ig==", "$type" : "03" }] } }should be a valid query in Mongo Compass since it is in Java AND the following error which is returned from both query area and Mongo Compass Explain Plan should not occur for such a query:
cannot nest $ under $inOne should NOT have…
1 vote -
Cast _id: number to string
Every time I type { _id: 12345 } in the Filter, I get zero results, until I realize that I forgot the quotes. Could Compass automatically convert numeric _id values to strings before running the query?
1 vote -
Display/use escaped characters like "\n" for line break in document editor
I have text fields that may contain "invisible" special characters like a line-break, which is commonly represented as "\n". Another example might be "\t" for tab, but there may also be other invisible unicode characters.
I would like to be able to edit/save documents in MongoDB Compass that contain such characters.
The current behaviour is that these characters are completely lost when the document is in edit mode and saved (updated). Manually inserting "\n" in a text field does not insert a line break, but literally a backslash + "n".
Example document:
{
"_id": "***",
"text": "Hello,\n\nThis is my message."…1 vote
- Don't see your idea?