#25747: djorm-ext-filtered-contenttypes impossible on Django 1.9
-------------------------------------+-------------------------------------
Reporter: mpasternak | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.9b1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgresql db | Triage Stage:
contenttypes | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by mpasternak):
#3006 is similar but different.
My app is a drop-in replacement for GenericForeignKey, you just replace
this with FilteredGenericForeignKey in model definition and you're set.
You don't need to use any functions, just the ORM. #3006 uses additional
function to achieve that.
Also, I'd need to have a look at queries generated by #3006. My module is
built for PostgreSQL and efficiency; if you index both (content_type_id,
object_id) fields, my module is going to produce queries that will make
PostgreSQL use that index.
Also, I don't support aggregate() and annotate() in my module.
--
Ticket URL: <https://code.djangoproject.com/ticket/25747#comment:3>
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/068.1581de69b640a0f93f286c962f4ac519%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
