#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 timo):
The usefulness of adding something like the following seems very limited
to me:
"If you are using PostgreSQL and add a field called 'name' to an existing
model but forget to add the column in your database, SELECT statements
will appear to work even though the column doesn't exist (since NAME is a
Postgres function and SELECT foo.name FROM foo is equivalent to SELECT
name(foo) FROM foo) ."
but since the ticket has been accepted, is that the essence of what is
being suggested?
--
Ticket URL: <https://code.djangoproject.com/ticket/15586#comment:16>
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.
