MrFreak

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=Xenithar]Wiki page is wrong. Look at the "Nullable" column. Every item is set to "NOT NULL", but they default to NULL. Another problem is that a primary key should NEVER be NULL. Base don these two facts, you would be required to put in a zero for a PK, but you should also remember that a PK should not change once set. Seems like that table is in need of a refit![/quote]

If you set NULL as the value for a primary key it will increment the value by 1 based on the previously highest number. You have to enable auto_increment for this.

I also noticed that the primary keys are the IDs for the realm so they are multiple times occurring. Problem is that a primary key should be unique but we got a lot of rows with the primary key value 1 so that is invalid. There should be a column called uptimeID or something like that which is the primary key. The reference on selecting or deleting stuff would happen on that uptimeID then and not anymore on the realmid which isn't unique.

I'm unsure why the column 'starttime' is a primary key. I don't see any use for that. It should be unique but not a primary key.

A quick node on your fix: You have to remove the `mangos`. of your SQL queries so the changes don't apply to a specific database but to the one which is currently open/selected. This prevents issues for people who have more than one database with different names than 'mangos'.

Can someone try if this works as a fix:

Change the rows faction_A and faction_H of the npc Dalinda Malem to the value 554.

The issue has been fixed with this commit: [url]https://github.com/mangosthree/server/commit/4b960bb1b5895f6675cf1ad5f0b2a79880a20f05[/url]