You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Database connection string with postgresql protocol assumes MongoDB #7687
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
changed the title [-]Postgresql prefix URI fallsback to MongoDB[/-][+]Database connection string with postgresql protocol assumed MongoDB[/+]on Nov 10, 2021
changed the title [-]Database connection string with postgresql protocol assumed MongoDB[/-][+]Database connection string with postgresql protocol assumes MongoDB[/+]on Nov 10, 2021
Activity
parse-github-assistant commentedon Nov 10, 2021
Thanks for opening this issue!
cbaker6 commentedon Nov 10, 2021
Seems like this could be added.
For reference: https://www.postgresql.org/docs/current/libpq-connect.html
Parse Server connects to Postgres using pg-promise->node-postgres. Reference uri: https://node-postgres.com/features/connecting
[-]Bug: Postgresql prefix URI fallsback to MongoDB[/-][+]Postgresql prefix URI fallsback to MongoDB[/+]mtrezza commentedon Nov 10, 2021
Classified this as a bug as the Parse Server docs say:
A "valid postgres URL" includes the
postgresqlprotocol, see docs:So it should work with either one. Severity low, as the workaround is to use the
postgresprotocol instead.[-]Postgresql prefix URI fallsback to MongoDB[/-][+]Database connection string with postgresql protocol assumed MongoDB[/+][-]Database connection string with postgresql protocol assumed MongoDB[/-][+]Database connection string with postgresql protocol assumes MongoDB[/+]parseplatformorg commentedon Jan 2, 2022
🎉 This change has been released in version 5.0.0-alpha.15
parseplatformorg commentedon Mar 15, 2022
🎉 This change has been released in version 5.0.0-beta.10
parseplatformorg commentedon Mar 18, 2022
🎉 This change has been released in version 5.1.0