New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow options to be a JSON object #12404
Conversation
Codecov Report
@@ Coverage Diff @@
## master #12404 +/- ##
==========================================
+ Coverage 90.28% 96.44% +6.15%
==========================================
Files 92 95 +3
Lines 8968 9114 +146
==========================================
+ Hits 8097 8790 +693
+ Misses 871 324 -547
Continue to review full report at Codecov.
|
Need some unit tests sequelize/test/unit/configuration.test.js Line 58 in c6e4192
|
Added test but for some reason it fails when run against a specific postgres test configuration, with a weird "leak" error, while it works perfectly on all others. As I'm really new to Node, any help is more than welcome. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, in future we can accept more keys for this sort of expansion other than options
Should I port this also to v5? My understanding is that the master is the latest (v6) version, right? |
Yes, you may open a PR for v5 branch |
This commit allows complex object to be passed as option in the URI connection string. For example it's now possibile to do something like:
so that it will be possible to correctly connect to an Azure SQL database, as encryption is required