#23940: ORM should allow model fields named "exact" -------------------------------------+------------------------------------- Reporter: zhiyajun11 | Owner: Type: Bug | Status: new Component: Database layer | Version: master (models, ORM) | 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 charettes): I suggest we open a new ticket to add field/lookup/transform collisions checks and add a test to my PR to make sure the reported issue doesn't regress. Thoughts? -- Ticket URL: <https://code.djangoproject.com/ticket/23940#comment:21> 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/068.282584f542f805ace3a090414c31ee18%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.