#33441: model Field.__hash__ should be immutable
-------------------------------------+-------------------------------------
     Reporter:  Adam Johnson         |                    Owner:  Adam
                                     |  Johnson
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  invalid
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):

 * cc: Simon Charette, Ryan Hiebert (added)
 * status:  assigned => closed
 * resolution:   => invalid


Comment:

 As far as I'm aware, fields are quite specific, in a real life they don't
 live without models. Field's hash should change when it's assigned to a
 model, comparing `creation_counter` is not enough. We shouldn't consider
 the same field instance assigned to a different models as equal. IMO the
 current behavior is expected, we don't want to reintroduce an issue fixed
 in 502e75f9ed5476ffe8229109acf0c23999d4b533.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33441#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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.3ca4583a9c57e00dbd0fb229e2ac463a%40djangoproject.com.

Reply via email to