Context Navigation

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

initial	v1
1	1	Besides the fact that it's existing production code, and using an Abstract model would change the database structure, there actually is one reason.
2	2
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).
	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).
4	4
5	5	Having 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//.