[DiscordArchive] <@!386224903084441611> so your proposal is to manually remove the duplicates?
[DiscordArchive] <@!386224903084441611> so your proposal is to manually remove the duplicates?
Archived author: Branel • Posted: 2021-04-21T06:11:21.127000+00:00
Original source
<@!386224903084441611> so your proposal is to manually remove the duplicates?
Archived author: Yehonal • Posted: 2021-04-21T07:03:47.131000+00:00
Original source
Thanks it works like a charm
Archived author: alchem1ster • Posted: 2021-04-21T08:26:06.328000+00:00
Original source
Why? We can leave only the first GUID match in the group, and from the second onwards we can delete them. So we leave only unique rows in the table. But here we have some questions.
1. We must check whether this will affect the operation of any events or scripts;
2. Is the first match (lowest GUID from group) sure to belong to some pool? It may happen that we delete exactly the GUID that is in the pool.
Archived author: alchem1ster • Posted: 2021-04-21T08:26:42.900000+00:00
Original source
If the question is how to remove it all - I can give you a list of all duplicate GUIDs. Except for the "original" of course
Archived author: Branel • Posted: 2021-04-21T08:34:03.897000+00:00
Original source
I just wanted to understand your idea
Archived author: Branel • Posted: 2021-04-21T08:34:35.849000+00:00
Original source
I am very interested in the idea
Archived author: alchem1ster • Posted: 2021-04-21T08:36:52.932000+00:00
Original source
Let's say I can bind to each item also the pool it is in (if it has one). Then we can probably painlessly remove those duplicate objects that are in the same pool.
Archived author: alchem1ster • Posted: 2021-04-21T08:39:00.549000+00:00
Original source
But I'm not sure that all found duplicates will have pools at all