32 results found

1. Date Tags for Easier Querying of Date Fields

   I propose adding a feature called "Date Tags" to MongoDB Compass, which would allow users to query date fields more easily. Date Tags would serve as shorthand for commonly used date queries, enhancing user efficiency and readability.

   Example Use-Case:
   Consider the task of finding all documents where the createdAt field was set to "yesterday". Normally, the query would look something like:

   {
     "createdAt": {
       "$gte": ISODate("2023-10-17T00:00:00"),
       "$lt": ISODate("2023-10-18T00:00:00")
     }
   }
   

   With Date Tags, this could be simplified to:

   {
     "createdAt": #yesterday
   }
   

   Proposed Date Tags:
   #today
#yesterday
#lastNDays
#lastNHours
#lastNMinutes
#others

   Each tag would automatically be translated to the corresponding MongoDB date query format.

   This feature is inspired by a similar implementation in Studio3T, and I believe it would be a valuable addition to MongoDB Compass as well.

   I propose adding a feature called "Date Tags" to MongoDB Compass, which would allow users to query date fields more easily. Date Tags would serve as shorthand for commonly used date queries, enhancing user efficiency and readability.

   Example Use-Case:
   Consider the task of finding all documents where the createdAt field was set to "yesterday". Normally, the query would look something like:

   {
     "createdAt": {
       "$gte": ISODate("2023-10-17T00:00:00"),
       "$lt": ISODate("2023-10-18T00:00:00")
     }
   }
   

   With Date Tags, this could be simplified to:

   {
     "createdAt": #yesterday
   }
   

   Proposed Date Tags:
   #today
#yesterday
#lastNDays
#lastNHours
#lastNMinutes
#others

   Each tag would automatically be translated to the corresponding… 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

   0 comments  ·  Queries  ·  Edit…  ·  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. 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

   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

   0 comments  ·  Queries  ·  Edit…  ·  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. Change collection on a saved query

   In the My Queries section it would be nice to be able to select which collection you want to be able to run the query against or to be able to copy the query to another collection.

   At the moment each query is 'locked' to the collection it was oringally created for.

   This means if i want to run the same query against another collection i have to open it and copy the text from the aggregation pipeline from the query then open the collection i want to run it on and copy the text into the aggregation pipline.

   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

   0 comments  ·  Queries  ·  Edit…  ·  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. 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 from the objectId.

   can we do anything that generation in the objectId based on the numbers or can we have anything like alphabetic have separate numbers like using the let variable like what we did for getting the months and days.

   if you do any one of them we can do auto-generation which is unique in numbers for every document either changing in the generation in objectId or adding the alphabetic to numbers like months and days

   I am sending the query that I have used in my organization for testing purposes but the result is unexpected so can you guide me on the correct to do it or any changes can you do in the upcoming release it can be appreciated. this is the basic suggestion from my side.I am thinking why don't we do it in the MongoDB other than going to python for random values.

   mongodb: For random numbers to generate based on the _id:

   If you insert the sample of 1k documents and test this query you will duplicates in the numbers and the count will also decrease.

   1st Method: [
   {
   $addFields: {
   numbers: {
   $regexFindAll: {
   input: {
   $toString: "$id",
   },
   regex: "[0-9]+",
   },
   },
   alpha: {
   $regexFindAll: {
   input: {
   $toString: "$id",
   },
   regex: "[a-z]+",
   },
   },
   },
   },
   {
   $project: {
   numbers: {
   $reduce: {
   input: "$numbers.match",
   initialValue: "",
   in: {
   $concat: ["$$value", "$$this"],
   },
   },
   },
   },
   },
   {
   $group: {
   _id: "$numbers",
   },
   },
   {
   $count: "string",
   },
   ]

   2nd Method:

   {
   $let: {
   vars: {
   monthsInString: [
   "",
   "JAN",
   "FEB",
   "MAR",
   "APR",
   "MAY",
   "JUN",
   "JUL",
   "SEP",
   "OCT",
   "NOV",
   "DEC",
   ],
   },
   in: {
   $arrayElemAt: [
   "$$monthsInString",
   {
   $toInt: {
   $dateToString: {
   format: "%m",
   date: "$dtCollected",
   },
   },
   },
   ],
   },
   },
   },

   Like this can you do for alphabetics so that we can convert the alphabetic to numbers then we can have random values which are unique in numbers .

   Can you please check and let me know if any changes I have done wrong from my side or any other way to generate the random values in numbers in the project stage.

   Why don't we do in mongodb instead of going to python for some random number which have unique values.

   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… 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

   0 comments  ·  Queries  ·  Edit…  ·  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

5. 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 from the objectId.

   can we do anything that generation in the objectId based on the numbers or can we have anything like alphabetic have separate numbers like using the let variable like what we did for getting the months and days.

   if you do any one of them we can do auto-generation which is unique in numbers for every document either changing in the generation in objectId or adding the alphabetic to numbers like months and days

   I am sending the query that I have used in my organization for testing purposes but the result is unexpected so can you guide me on the correct to do it or any changes can you do in the upcoming release it can be appreciated. this is the basic suggestion from my side.I am thinking why don't we do it in the MongoDB other than going to python for random values.

   mongodb: For random numbers to generate based on the _id:

   If you insert the sample of 1k documents and test this query you will duplicates in the numbers and the count will also decrease.

   1st Method: [
   {
   $addFields: {
   numbers: {
   $regexFindAll: {
   input: {
   $toString: "$id",
   },
   regex: "[0-9]+",
   },
   },
   alpha: {
   $regexFindAll: {
   input: {
   $toString: "$id",
   },
   regex: "[a-z]+",
   },
   },
   },
   },
   {
   $project: {
   numbers: {
   $reduce: {
   input: "$numbers.match",
   initialValue: "",
   in: {
   $concat: ["$$value", "$$this"],
   },
   },
   },
   },
   },
   {
   $group: {
   _id: "$numbers",
   },
   },
   {
   $count: "string",
   },
   ]

   2nd Method:

   {
   $let: {
   vars: {
   monthsInString: [
   "",
   "JAN",
   "FEB",
   "MAR",
   "APR",
   "MAY",
   "JUN",
   "JUL",
   "SEP",
   "OCT",
   "NOV",
   "DEC",
   ],
   },
   in: {
   $arrayElemAt: [
   "$$monthsInString",
   {
   $toInt: {
   $dateToString: {
   format: "%m",
   date: "$dtCollected",
   },
   },
   },
   ],
   },
   },
   },

   Like this can you do for alphabetics so that we can convert the alphabetic to numbers then we can have random values which are unique in numbers .

   Can you please check and let me know if any changes I have done wrong from my side or any other way to generate the random values in numbers in the project stage.

   Why don't we do in mongodb rather than python.

   can you please add this secenrio

   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… 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

   0 comments  ·  Queries  ·  Edit…  ·  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

6. 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

   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

   0 comments  ·  Queries  ·  Edit…  ·  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

7. 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 $in
   

   One should NOT have to change the query from what a client program naturally uses (the dollar signs) to

   { "_id" : { "$in": [ BinData(3, "6Uk1UVZWl+krPObxzA3wtg=="), BinData(3, "60Xp1sJ9nMiT6cPy3GA1ig==") ] } }
   

   I suspect that this change would be to augment the underlying query language, but, the exact implementation to having a tool which can tell me whether the exact query Java is using will be using the index is something which would be up to Mongo Corporation debate.

   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 $in
   

   One should NOT have… 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

   0 comments  ·  Queries  ·  Edit…  ·  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

8. 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.

   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

   0 comments  ·  Queries  ·  Edit…  ·  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

9. 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 }.

   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

   0 comments  ·  Queries  ·  Edit…  ·  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

10. 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

    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

    1 comment  ·  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

11. 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."
    }

    If I edit this document, e.g. changing the "." at the end of the text to a "!" it would be saved as "Hello,This is my message!"

    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."… 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

    1 comment  ·  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

12. 点击按钮没反应

    点击Export To Language 白屏，无反应，系统信息：macos 10.14.6 (18G2022)

    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

    1 comment  ·  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