QUOTE(snowblink @ Dec 18 2008, 02:00 PM)
Simplest way to describe it:
I add a card to my inventory or wantlist. It is the only card from the set, and only card for that player in my whole inventory/tradelist.
Run the update my interest from inventory/tradelist in tools.
This creates "interest flags" for the card set, the player.
Time goes along...I trade the card out of my inventory.
So I remove the entry for the card, and run the update my interest tool.
The entry disappears from the set inventory/tradelist rollup.
However, the entry for the player is not removed. It appears in the player rollup with 0 0 0. So I have to then go in and manually "remove interest" for that player record, then run the update my interest tool. Where I would have thought once no more cards for the player existed in wantlist/inventory that a cascade removal from the player rollup would occur.
So I guess the best way to describe form a data standpoint is there is no, or not correctly functioning, cascading update for that data update situation.
Hope that helps to describe it.
(It's not a huge deal now that I know what to do to resolve it.)
QUOTE(bob_TCC @ Dec 18 2008, 02:05 PM)
Thanks, snowblink. That is very helpful.
My initial reaction is that I actually don't know that adding a card of a player should automatically assume an "interest" in the player. Eventually, you might find that you have an "interest" in just about every player (based on the size of your inventory) - even though you really only care about a handful of players.
QUOTE(snowblink @ Dec 18 2008, 02:11 PM)
That's what I thought at first too, although from a programming standpoint I understand why those "interest flags" are important for producing the inventory/wantlist snapshot rollups, and for search purposes.
That's why I'm a bug reporter, not a programmer.
Thanks for the detailed description.
I'll first say that our use of the term "interest" is being used loosely.
It does not mean you have a collecting interest. That is set differently.
I know of the bug and I bet if you run the tool again it will clear it up. I pushed out a fix last night that cleared it for me. A confirmation of that would be awesome.