#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
-------------------------------+--------------------------------------------
Changes (by mtredinnick):
* stage: Design decision needed => Accepted
Comment:
This is needed functionality. I'm not wrapped in the proposed syntax for
column naming, though. Since there are only going to be two columns, we
can probably get away with just making them each an attribute (but you
have to specify both or none, I guess). Something like {{{self_col_name}}}
and {{{remote_col_name}}} would work.
I can't see any reason not to implement this if somebody feels so
enthused. It shouldn't be too hard: mostly some fiddling around in
{{{django/core/management.py}}} for the initial table creation and
{{{django/db/models/related.py}}} for setting up the related class
correctly at model creation time, I would guess.
--
Ticket URL: <http://code.djangoproject.com/ticket/785#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
