#22514: Postgres index generator does not expect db_type to be None -------------------------------------+------------------------------------- Reporter: vzima | Owner: vzima Type: Bug | Status: assigned Component: Database layer | Version: 1.6 (models, ORM) | Resolution: Severity: Normal | Triage Stage: Ready for Keywords: | checkin Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by vzima):
* owner: nobody => vzima * status: new => assigned * has_patch: 0 => 1 * stage: Accepted => Ready for checkin Comment: I've made a PR from the patch. PR: https://github.com/django/django/pull/2687 This patch only patches up the postgres issue. It might be worth to not generate indexes on virtual fields in general. -- Ticket URL: <https://code.djangoproject.com/ticket/22514#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 post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/063.1a0faf52122fc2d52c27a68c0dc29e23%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.