Skip to content
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

Exception while using the connection string with postgres #186

Closed
zugspitze opened this issue Sep 30, 2022 · 5 comments
Closed

Exception while using the connection string with postgres #186

zugspitze opened this issue Sep 30, 2022 · 5 comments

Comments

@zugspitze
Copy link

Hi, I am getting the following exception when using the connection string.

engine = SCHEMES[url.scheme] if engine is None else engine KeyError: 'postgresql+psycopg2'

Also my connection string starts with postgresql+psycopg2

Can you please suggest me how to fix it?
Thanks!

@mattseymour
Copy link
Contributor

Do you have any more context around this issue?

@palfrey
Copy link
Contributor

palfrey commented Dec 13, 2022

Two PRs for this:

@mattseymour
Copy link
Contributor

The connector for postgres connections is postgres no need to use the +psycopg connection part. This is because under the hood it uses the same Django postgres connector. I would say we do not support adding aliases and instead improve the error handling. As I see @palfrey has suggested in another message.

@palfrey
Copy link
Contributor

palfrey commented Dec 15, 2022

The connector for postgres connections is postgres no need to use the +psycopg connection part. This is because under the hood it uses the same Django postgres connector. I would say we do not support adding aliases and instead improve the error handling. As I see @palfrey has suggested in another message.

Happy for me to merge #196 then?

@palfrey
Copy link
Contributor

palfrey commented Dec 21, 2022

@zugspitze With the current master branch of this repo, you should now get a better error message, and so should be clear to change the schema to postgres now.

@palfrey palfrey closed this as completed Dec 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants