2012-03-07, 07:59 AM
SaptaZapta Wrote:I'd also like to point out that the "item ID" method, besides being inefficient, does nothing against the duping of stacks and stacks of "rare" scrolls, recipes, or crafting materials.
Not true actually, if you can't duplicate the stack in the first place you can't unstack and reshuffle to hide the fact you've done it.
Stacking just prevents them from being able to spot duplicate IDs after the fact by merging everything into new IDs, but if it threw a PK constraint and never let the second item/stack exist it'd cut off the issue before it happens and could be hidden. That aside, the other flaws with a unique constraint on a DB this size still apply and make it potentially infeasible.
It's not having what you want - It's wanting what you've got.