#785: many2many table and legacy databases.
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Status: new | Component: Database wrapper
Version: | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------+--------------------------------------------
Comment (by mtredinnick):
Replying to [comment:5 russellm]:
> Replying to [comment:4 mtredinnick]:
>
> For the benefit of anybody approaching this problem; I'm agreed that two
attributes is better than a tuple. Two columns isn't a burden, and there
is always the possiblity that one of the default names will be correct.
Agreed.
>
> However, all the other database column/table naming fields in Django are
prefixed with db_ (db_column, db_table). It's probably a good idea to keep
this convention. db_m2m_column and db_m2m_reverse, perhaps?
Where "reverse" means "moving further away from this model to the one on
the other side of the intermediate table"? Hmmm. :-)
I agree with your real point, though: names matching the db_* pattern
would be better. Let's see what the patch creator comes up with.
--
Ticket URL: <http://code.djangoproject.com/ticket/785#comment:6>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
