You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We know that a given entity can act both as bidder and buyer. Does such an entity appear in the Digiwhist dataset with 2 different UUIDs, one for the bidder and one for the buyer role?
If so querying on Actor.name will yield duplicate results because this entity will appear two times.
If not then our architecture is flawed because inserting a Buyer if a Bidder exists with the same id will result in duplicate key error on Actor.id.
The text was updated successfully, but these errors were encountered:
I created the Actor base class for Bidder and Buyer to make actor-centric networks easier to manage.
The rationale was that our users don't think in terms of roles but in terms of entities and we assume that when they filter by entity they want to see it in the network in both roles.
However, the risk of failing imports is too high for this gain so I think we should at least remove the id field from Actor. We could keep the Actor class just as a category to make queries on both roles simultaneously easier.
I ended up removing the Actor class for good for reasons explained in #50 so technically this is no longer a bug.
As for the answer, it is still relevant but I don't have it at the moment so I'll leave this issue open but move it far in the backlog for it will be easy to answer once we have all the data in.
We know that a given entity can act both as bidder and buyer. Does such an entity appear in the Digiwhist dataset with 2 different UUIDs, one for the bidder and one for the buyer role?
If so querying on
Actor.name
will yield duplicate results because this entity will appear two times.If not then our architecture is flawed because inserting a
Buyer
if aBidder
exists with the same id will result in duplicate key error onActor.id
.The text was updated successfully, but these errors were encountered: