Can't insert relationship with same object twice about spine-database-api HOT 8 CLOSED

In GitLab by @manuelma on Jan 3, 2019, 20:07

I believe this is intentional, but of course if there's doubt we should open it for discussion. What do you think @juha_k @DillonJ should we allow the same object to appear twice in one relationship?

from spine-database-api.

In GitLab by @PvPer on Jan 4, 2019, 08:32

So for me the reason I wanted to insert a relationship with one object twice was when i had a unit water_turbine with input water and output water and electricity. In this case I want to constraint the input water to be the same as the output water so I needed to use the unit__commodity_group_in__commodity_group_out where the commodity_group was the same object.

I don't really see why we should forbid to use the same object twice, what's the reasoning behind that?

from spine-database-api.

In GitLab by @manuelma on Jan 4, 2019, 13:17

Thanks @PvPer I believe your use case makes a lot of sense. I had decided to forbid that just to help the user not do something stupid. We can allow it if everybody is on board.

from spine-database-api.

In GitLab by @manuelma on Jan 24, 2019, 16:10

The more I think about it, the more it makes sense to release that constraint (i.e., allow the same object to appear more than once in one relationship) Any thoughts @spine ?

from spine-database-api.

In GitLab by @mihlema on Jan 24, 2019, 16:27

I do agree @manuelma

from spine-database-api.

In GitLab by @jkiviluo on Jan 25, 2019, 10:11

I also think it should be allowed (and is needed in some cases).

from spine-database-api.

In GitLab by @manuelma on Jan 25, 2019, 21:40

Check removed in last dev.

from spine-database-api.

In GitLab by @manuelma on Jan 25, 2019, 21:40

closed

from spine-database-api.