#12296: optional reverse model relation
------------------------------------------+---------------------------------
 Reporter:  discoloda                     |       Owner:  nobody    
   Status:  new                           |   Milestone:            
Component:  Database layer (models, ORM)  |     Version:  1.1       
 Keywords:                                |       Stage:  Unreviewed
Has_patch:  0                             |  
------------------------------------------+---------------------------------
 My current project has a often referenced table, there is no value in
 having related tables. The project is split with many applications with
 table names such as Instance (an instance of the primary model in that
 app). having collisions in the backward related resolver causes me be
 creative with names that I will never use.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/12296>
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.


Reply via email to