Drivers
5 results found
-
add deno driver
(i was forced to select a category so i choose nodejs)
Deno is coming https://deno.land/
From the creator of nodejs. Better than nodejs.
5 votes -
Support getting connection provider when connecting with aws authentication
It would be helpful if the connect function would support getting one of "@aws-sdk/credential-providers", in case of AWS authentication.
see:
https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/modules/_aws_sdk_credential_providers.html#fromNodeProviderChainReason:
mongo db driver for node js, checks the credentials in specific order, and gives precedence to env. There is no way to override it.
This causes a problem when running from EKS cluster, and using web identity token file.
When my pod needs to access also other AWS resources like S3, and I expose AWS environment variables (like AWSACCESSKEYID, AWSSECRETACCESSKEY), the MongoDB driver takes into account the credentials before the web identity…1 vote -
Support "default" keyword in MongoDB's implementation of JSON Schema
Without defaults, there is a need to iterate though each property just to check if a default value is needed (most probably this can be easily done on type check). Also without defaults we need to remember checking it both in inserts and updates (for example with $push operator)
1 vote -
Add some casting addon or function based on MongoDB's implementation of JSON Schema
Without casting addons, there is a need to iterate though each property just to check if this value needs some casting (most probably this can be easily done on type check). I´m having special troubles with Date type, as most of the time this type is send as an ISO string, but saved in the DB as a DATE
1 vote -
A tool to test the connection that can fix resolution issues in server selection
This is probably not Node Specific a general problem with connecting via a seed list.
ServerSelection via seed list is a great concept. It works poorly. I have attached an hour of starting a working webserver app and 30 times starting it in a little over an hour. It failed to connect over 40 % of the time. A larger amount of successful connections were made over 35 seconds which means they would fail in a hosting environment like Heroku. Only 10% of the time did it connect in < 6 seconds. Your support team is avoiding using seed lists…1 vote
- Don't see your idea?