Was responding to the first example you gave, which was a fairly bad example since it just ensures all separate identifier fields are the correct size (since everybody defines their own).
In the case of the new example, I only did that for supports sake (if somebody swaps from another multicharacter that stores in a similar format, or swapped away from my own).
My own personal build of ESX and Multicharacter stores differently
Really the worse example is the multiple queries when deleting a character, which requires setting up foreign keys to resolve… most people can’t run an SQL file so…