#12279: prepare_database_save in add_update_fields makes some custom fields be
impossible.
-------------------------------------+-------------------------------------
     Reporter:  bear330              |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  closed
    Component:  Database layer       |                  Version:  1.1
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  wontfix
     Keywords:                       |             Triage Stage:
  prepare_database_save,             |  Unreviewed
  ObjectField, ClassField            |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by sebitoelcheater):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 So, how did you handled this wontfix situation? Did you implement a
 working ClassField?

-- 
Ticket URL: <https://code.djangoproject.com/ticket/12279#comment:4>
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/065.6907df00862b71ea4d98ef74af631bff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to