#29147: Postgres JSONField missing to_python
-------------------------------------+-------------------------------------
Reporter: Javier Buzzi | Owner: Williams
| Mendez
Type: Bug | Status: closed
Component: contrib.postgres | Version: 1.9
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Javier Buzzi):
As i understood it was that `to_python()` is the representation of the
data in python, postgres could save it and do with it what it wants; store
it binary/urlencode it/ encrypt it for all it wants, but from a python
perspective that data to me, needs to be represented as a dict/simple type
(if it is "hello") -- i still don't understand why this is invalid.
--
Ticket URL: <https://code.djangoproject.com/ticket/29147#comment:5>
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/069.15c0a0558958c5bea8c9625bfe2795e6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
