#23335: Related fields pointing to custom fields that store different values in
the
database than the python representation do not remember selections
---------------------------+--------------------------------------
Reporter: thenewguy | Owner: nobody
Type: Bug | Status: closed
Component: Forms | Version: 1.7-rc-2
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------+--------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0
Comment:
I spent some time looking at this, but ultimately, I couldn't determine
whether this was a bug in Django or in your own code. It would be helpful
if you could provide more details about where you think the problem lies.
By the way, there are [https://github.com/django/django/pull/3047 plans to
deprecate] `SubFieldBase`. Your issue may still be valid, but I thought
I'd mention it so you are aware.
--
Ticket URL: <https://code.djangoproject.com/ticket/23335#comment:1>
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/067.773bcc4ab2b39813524b0762517117e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
