|
|
and i see that going horribly wrong because it's a non obvious change to the user |
|
|
|
i don't see the reasoning behind that. what has the user to do with anything here.
to maintain a cleaner database, this would be perfect, as really nobody checks "the other side" when adding those relations (well maybe nwa does). so forcing the state to ended when it really can't exist anymore would be very smart behaviour. |
|
|
|
It is indeed a smart and automative way of handling the relations. You just have to be really sure about the creator or company being dead. For people there's little room for mistake, for companies it's a bit riskier I suppose. Then there's also the issue with retroactively adding relations and to "dead" creators, should these be also automatically set to ended. And of course the relation "is the founder of/was founded by" should be excluded, in fact, it shouldn't ever be possible to set that relation as "ended". |
|
|
Hinoe
2015-04-14 17:34
reporter
~0003551
Last edited: 2015-04-14 17:35
|
There are instances where this can go rather wrong. For example, assuming woman X dies, man Y ceases to be her husband, okay, that makes sense. But what if they die together in, say, a car wreck or a plane crash, did their relation ever end in the proper sense of that term? A way for a mod to override that needs to be present to handle such exceptions. And to port here what nwa mentioned on issue 0002272, aside the founder relation, the family one should never be settable to ended, ever (though this brings up the question of stepfamilies, if your stepmother divorces your father do you cease being her family? oh god I think I may have opened a can of char relation worms...).
|
|
