#10028: Incorrect SQL join construction
---------------------------------------------------+------------------------
Reporter: brian | Owner: mtredinnick
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by mattrussell):
The names of the fields you've defined are shadowing the names of the
classes.
i.e you cannot name a class "software" then use "software" as a attribute
name for a field on another class (in the same module.
Python won't stop (or warn) you about this, but a tool such as
pylink/pychecker would.
(nb. this is how python scoping works)
I'd be surprised if naming your classes in camel case notation (as PEP8
suggests) doesn't fix your problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/10028#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
-~----------~----~----~----~------~----~------~--~---
