#15586: Fields with missing columns populated when querying on PostgreSQL
-------------------------------+------------------------------------
Reporter: sebzur | Owner: nobody
Type: Bug | Status: reopened
Component: Documentation | Version: 1.2
Severity: Normal | Resolution:
Keywords: postgresql | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by lrekucki):
Note that "name" is just an example here. From my understanding, you can
swap it to any other datatype that PostgreSQL supports and instead of
raising an error about a missing column, it will treat it as a cast of the
whole row to that datatype.
Anyways, I tried this on PostgreSQL 9.2 and the behavior is no longer
there. I'm guessing it was removed in version 9, but don't have an
instance to verify.
--
Ticket URL: <https://code.djangoproject.com/ticket/15586#comment:17>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
