Table dbscripts_on_creature_movement has no unique ids for primary key

OLD dbdocs used by accident and talked with Ants. The script_ids uniqueness refers to the id of each script. This is unique because it is calculated as id + delay which gives you a composite key between them. Delay field is responsible for the sequential execution of them.

[quote=MrFreak]This is unique because it is calculated as id + delay which gives you a composite key between them. Delay field is responsible for the sequential execution of them.[/quote]
Not that exactly. The world table structure is more or less reasonable and elaborated. If you do not see the key composed of the two fields, then it's not a key. Nothing prevents us to define several script commands with the same delay, i.e. executed at the same moment of time. The execution order remains undefined though.

The dbscript_on_* tables should be moved as a whole to the same trash bin as EventAI engine, being substituted by something like TC's SmartAI. However, even TC's SmartAI has yet no full support for this (for instance, spell events not related to gameobjects, so the SmartAI cannot substitute dbscripts_on_event).