Update - Disconnects and Latency Issues

It's as simple as this;

Code:

BEGIN TRANSACTION
INSERT INTO ItemSlot_ETC
SELECT * from ItemLocker where
where characterid = 1 and accountid = 2 and sn = 99999;

DELETE FROM ItemLocker where
characterid = 1 and accountid = 2 and sn = 99999;
COMMIT TRANSACTION;

And suddenly the two are a single discrete block of logic. They both write their end results together, or not at all. Voila. Duping no longer possible.

Duping being possible at all is ridiculous.

Love how simple you've put it. It really is that simple, and yet from what I gather, Nexon hasn't even TRIED anything like this. What you've stated is a simple and routine coding/scripting practice to prevent things such as dupes and for avoiding interrupted/incomplete logic.