#24726: ArrayField with IntegerRangeField as base field generates invalid SQL on
Insert operations
----------------------------------+------------------------------------
Reporter: edrmp | Owner: adamzap
Type: Bug | Status: assigned
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 adamzap):
https://github.com/Crossway/django/commit/718bfaa18a12fb059d9e5cf8c4c716402ac8cb4d
This patch integrates and updates the contributions from edrmp and
dvarrazzo above. The tests pass, but I'm not sure I put the psycopg2
adapter bits in the right place. I guess this is more a proof of concept.
I think there needs to be more discussion about how arrays of range fields
should work. Lookups don't work right now, and I'm not sure how they
would.
Also, dvarrazzo's suggestion to subclass NumericRange works, but wouldn't
that require range objects destined for the database to be created with
the adapted subclasses? I'm not sure if that's desired for Django. I'm
interested to hear what the core team thinks.
Anyway, I hope this patch is helpful!
I'm unassigning this ticket for now as I don't think I can make progress
without some design discussion taking place.
--
Ticket URL: <https://code.djangoproject.com/ticket/24726#comment:8>
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.9326d2d3f83f5ba8f711cf830a96fe84%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
