MongoDB slow queries stay empty until you enable the profiler
The panel names the command to run instead of showing a blank table, and the metrics beside it are omitted rather than reported as zero.
7 posts
Writing on MongoDB
Document browsing, aggregation pipelines, index introspection and agent mode over the native driver, bounded by a user proven read-only at open. Where it stops: No SQL translation layer is faked — queries here are MongoDB queries.
MongoDB has no constraint for a diagram to discover
The empty relation list here means impossible rather than none found, and the relationships a document model leaves for you to know live in the shape and in the pipeline.
The MongoDB editor takes a JSON command, not shell syntax
A statement beginning db. cannot run here at all, and the two operations that look alike have very different default bounds on the result set.
The MongoDB field list is inferred from a hundred documents
There is no catalog to read, so the sidebar samples each collection and states its own reach - three levels deep, arrays closed, two hundred fields.
The MongoDB login failure that is not a wrong password
authSource names the database the credentials live in, not the one you are opening, and getting it wrong fails exactly like a bad password.
Connecting to MongoDB Atlas and what the URI decides for you
An SRV URI implies TLS in the driver and maps the form to a verifying mode, but two of the five SSL choices build the same options object.
Plan mode on MongoDB, where the safety checks decline
The read-only guard and the identifier reader are SQL readers, so on a MongoDB draft they record that they do not apply instead of passing it.