Changes between Initial Version and Version 1 of Ticket #28110, comment 3


Ignore:
Timestamp:
04/21/2017 07:34:39 PM (2 years ago)
Author:
Matthew Schinckel
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28110, comment 3

    initial v1  
    11Besides the fact that it's existing production code, and using an Abstract model would change the database structure, there actually is one reason.
    22
    3 A different model has a relationship to OrgUnit, and from the perspective of that model, it's important that it doesn't need to know which of the OrgUnit subclasses it relates to (i.e., as long as it relates to _any_ OrgUnit, that's fine).
     3A different model has a relationship to OrgUnit, and from the perspective of that model, it's important that it doesn't need to know which of the OrgUnit subclasses it relates to (i.e., as long as it relates to //any// OrgUnit, that's fine).
    44
    55Having said that, I'm not entirely happy with that model structure, and I plan at some point to move it to a better structure (I have a similar setup that allows an arbitrary number of levels of hierarchy, for instance). However, I can't change that //right now//.
Back to Top