#15586: Field populated when no DB column present
-----------------------------------------+----------------------
Reporter: sebzur | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: 1.2
Resolution: wontfix | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
-----------------------------------------+----------------------
Comment (by sebzur):
Of course testing the synchronization between the Django models & db
schema every time would be a stupid idea - that was not my point.
Also, I was not asking for automated schema evolution, which is quite a
tricky issue and in most cases, for complex DB schema updates, You just
have to handle
it manually on your own.
I was just curious HOW 'SELECT' statement could retrieve something from
database, when there was no column to get from?
Once again I try to describe the proces:
- model MyMode was created and db was synced
- to model was added a CharField and I did not create corresponding DB
table on my own
- I performed qs = MyMode.objects.all(), that I had something in:
qs[0].name, qs[1].name and so on ... which I do not understand how this
field was field when there was no data in DB? It looks to me like an
unexpected behavior....
I would appreciate Your further comments.
--
Ticket URL: <http://code.djangoproject.com/ticket/15586#comment:2>
Django <http://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.
