#24726: ArrayField with IntegerRangeField as base field generates invalid SQL on
Insert operations
----------------------------------+------------------------------------
Reporter: edrmp | Owner:
Type: Bug | Status: new
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by mjtamlyn):
This is a tricky one to fix. My inclination is that half the fault lies
with postgres, and perhaps it could be fixed with psycopg2 as well.
The nicest solution is to add a {{{::int4range[]}}} at the end of the
parameter, but doing that is tricky to implement. It should be possible to
register a custom typecaster for arrays of ranges with psycopg2. It feels
like it should just work though...
I have raised https://github.com/psycopg/psycopg2/issues/313 with psycopg2
to get their feedback.
--
Ticket URL: <https://code.djangoproject.com/ticket/24726#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.d64564f5c3ae9d4ae3e7669f3e6e28fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
