#35136: Interoperability with intarray PostgreSQL extension
     Reporter:  Jan Hamal Dvořák     |                    Owner:  (none)
         Type:  New feature          |                   Status:  closed
    Component:  contrib.postgres     |                  Version:  dev
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:  postgresql,          |             Triage Stage:
  intarray                           |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
Comment (by Jan Hamal Dvořák):

 Thank you for a timely reply.

 > I don't think that Django can commit to producing SQL that is compatible
 with all the combination of usage of Postgres extensions out there.

 I feel this is somewhat unfair. I am not asking for perfect support of
 every possible extension out there. Django already supports multiple
 PostgreSQL extensions. The `intarray` is another one of the handful of
 extensions bundled with PostgreSQL and available out of the box on
 mainstream Linux distributions. It doesn't feel like a stretch to expect
 Django won't break if I enable it, but I won't press you.

 Thanks for a cleaner workaround.
Ticket URL: <https://code.djangoproject.com/ticket/35136#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to