optional reverse model relation
|Reported by:||discoloda||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||1.1|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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.