#15586: Fields with missing columns populated when querying on PostgreSQL
-------------------------------------+-------------------------------------
Reporter: sebzur | Owner: nobody
Type: Bug | Status: reopened
Milestone: | Component: Database layer
Version: 1.2 | (models, ORM)
Resolution: | Severity: Normal
Triage Stage: Design | Keywords: postgresql
decision needed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
-------------------------------------+-------------------------------------
Changes (by sebzur):
* easy: => 0
Comment:
After a few weeks I'm returning to this issue. To summarize what we see,
let me point out the two elements:
- the issue has rather low probability to appear: You have to use PG
backend + You have to have Your model defining non-existing (in DB schema
sense) field/column
- I feel this is also a kind of a issue in PostgreSQL itself
What we should do now, is **for sure** to document this behavior --- while
it's not clear in DB engine itself what does it mean to `select column
from table`, I believe Django should not be smarter in handling it in
other way than the engine does it.
--
Ticket URL: <http://code.djangoproject.com/ticket/15586#comment:14>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
