@bembelimen Can it be you have forgotten a word "not" in your description?

The stage ID should not be part of the key, because otherwise you could add something like: (1, 1, 'com_content'), (1, 2, 'com_content'), which is not correct.

If you have the stage ID in the primary key (PK), you can't add those examples, if you don't have the stage ID in your PK, you can add them.

And "otherwise" refers to the opposite of the part of the sentence before that, and so it means that the stage ID would be part of the PK.

So I think you meant:

The stage ID should not be part of the key, because otherwise you could not add something like: (1, 1, 'com_content'), (1, 2, 'com_content'), which is not correct.

Correct me if I'm wrong.

Each item (item_id, extension) can have only one stage, ex 'published'.

Why are there so many index keys? At least one key is redundant (idx_item_id).

@csthomas So this PR is wrong?

PR is correct.

On the other hand I do not like this table #__workflow_associations at all.
It seems to be better to add additional column stage_id in #__content and remove this table at all.

@bembelimen Forget my comment to you above at the top. I was confused somehow. Your description is correct.

I have tested this item ✅ successfully on d347650

I have tested this item ✅ successfully on d347650

Thanks!