#32588: Exception handling in contrib.postgres
----------------------------------+--------------------------------------
Reporter: Jan Holas | Owner: (none)
Type: Bug | Status: closed
Component: contrib.postgres | Version:
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by Jan Holas):
Replying to [comment:1 Mariusz Felisiak]:
> Thanks for this report, however it's not supported to use the same
connection for different kind of databases. You can add a second database
connection and use 3rd-party backend for Redshift, e.g.
`django_redshift_backend`.
We have a separate database connection however we're still using psycopg2
to connect to Redshift which is perfectly fine as its PG compatible. The
exception handling and the comment there suggests that it's ok to use the
contrib.postgres for other features even if the underlying DB doesn't
support HStore extension.
--
Ticket URL: <https://code.djangoproject.com/ticket/32588#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.a811d8b933bdc338bdebd6871b5fd3d2%40djangoproject.com.
