Jason Jhuboo

My feedback

  1. 21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  3 comments  ·  Share your ideas with us  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jason Jhuboo commented  · 

    Fantastic news that this has been started - my use case is simple (and probably isn't the same as everyone else's requirement). I understand that the team at 3T will want to make this work for everyone, but I thought it best to provide our requirements anyway.

    - When making queries, we are happy to use the original database name (we don't particularly care about the query windows changing).

    - When looking for a database, we'd like to be able to see the alias for the database. It would be wonderful if this was somehow configurable, but as long as we could see it somewhere in the tree at a glance, it would make the UI a lot more usable for us. It would be nice to be able to sort on the Alias rather than the database name in the UI too.

    - Applying an alias to a database could be done in many ways. If it is some configuration within Studio 3T, it would be useful to be able to import/export this mapping so a development team can have the same view. Better still - it would be nice to be able to specify a particular database/collection to query for mapping values. This could then be extended programatically outside of Studio 3T, and an entire team would always have a consistent UX. Another way would be to do what Postman does and have shared configuration stored online and served to a team - but this seems like overkill when we've all got Mongo databases anyway.

    I hope this input is useful when it comes to designing this feature.

    An error occurred while saving the comment
    Jason Jhuboo commented  · 

    We have exactly the same problem - one MongoDB connection and we are projecting that we will have over 500 databases, and we name databases with Guid's to segregate data owned by different people. This feature would be a god-send, as it is slowly becoming unmanageable.

    Jason Jhuboo supported this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Share your ideas with us  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jason Jhuboo shared this idea  · 

Feedback and Knowledge Base