#35324: Postgres Extensions Not Available
----------------------------------+----------------------------------------
Reporter: Fred Lamming | Owner: Fred Lamming
Type: Bug | Status: closed
Component: contrib.postgres | Version: 5.0
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
----------------------------------+----------------------------------------
Changes (by Natalia Bidart):
* has_patch: 1 => 0
* resolution: => invalid
* status: assigned => closed
Comment:
Hello Fred, thank you for your report.
Could you please explain how Django (core) is at fault here? From your
description, this seems like an issue in django-tenants and it would be
best if you file and solve the issue there.
I'll be closing this ticket as invalid following the
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#closing-tickets ticket triaging process]. If, after debugging,
you find out that this is indeed a bug in Django, please re-open with the
specific details and please be sure to include a small Django project to
reproduce or a failing test case.
--
Ticket URL: <https://code.djangoproject.com/ticket/35324#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/0107018e628d41e2-0e8c6859-17e3-4e2c-b6b5-82701b931934-000000%40eu-central-1.amazonses.com.