Primary key already exists

I have same issue too

@timohuisman: not the same issue, which has been solved 8 months ago.

@brulain, as far as I can tell is the update hook that is causing this error introduced in [3205682]

Thanks timohuisman, but I should like to know how to fix it.

We've fixed it by skipping the update hook. We've verified that the primary key was already set so it doesn't had a lot of impact to skip the hook. I wouldn't recommend it if you can't verify the impact yourself.

The last run hooks are stored in the key_value table. There is probably a row system.schema | date_recur | i:8207;. If you increase the number to 8208 the update hook will be skipped next time you run your updates. But again, I wouldn't recommend this if you can't verify the impact.

Replaced by 🐛 Add primary key checks before adding them Active