Closed tjholm closed 3 weeks ago
@tjholm
Wondering if we need more than just the connection string for libraries that don't support it? Such as a DSN string with gorm etc. Perhaps add all the database connection variables so that the end user could format and build a string with them?
@tjholm
Wondering if we need more than just the connection string for libraries that don't support it? Such as a DSN string with gorm etc. Perhaps add all the database connection variables so that the end user could format and build a string with them?
Its a possiblity, to address GORM as a specific use case, it looks like standard connection strings are also supported (it used pgx parsing under the hood: https://github.com/jackc/pgx/blob/60a01d044a5b3f65b9eea866954fdeea1e7d3f00/pgconn/config.go#L233-L248).
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 49.25%. Comparing base (
5cd5cfe
) to head (50891ea
). Report is 1 commits behind head on main.:exclamation: Current head 50891ea differs from pull request most recent head 79747a0. Consider uploading reports for the commit 79747a0 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
WIP Proposal for SQL Database support as a nitric resource.