Changes between Initial Version and Version 1 of Ticket #29630, comment 7


Ignore:
Timestamp:
09/05/18 18:47:22 (4 years ago)
Author:
Simon Charette
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29630, comment 7

    initial v1  
    1 The ''easy picking'' flag is used for [https://docs.djangoproject.com/en/2.1/internals/contributing/triaging-tickets/#easy-pickings tickets that would require small, easy, patches]. For example a typo in an error message or something that be performed why a search and replace through the code base.
     1The ''easy picking'' flag is used for [https://docs.djangoproject.com/en/2.1/internals/contributing/triaging-tickets/#easy-pickings tickets that would require small, easy, patches]. For example a typo in an error message or something that be fixed with a search and replace through the code base.
    22
    3 Any ORM bug does't fit into this category. The fact it only manifests itself on Oracle which a most of contributors have limited knowledge of also makes it harder to resolve.
     3Any ORM bug does't fit into this category. The fact it only manifests itself on Oracle most of current contributors have limited knowledge of also makes it harder to resolve.
    44
    55I've switched the component to the database layer because while it manifests itself in the admin in your case such an ambigously defined query can be trivially constructed by using `select_related('fk')` or `values('id', 'fk__id')`.
Back to Top