The tables reinforcement_id and reinforcement are split and should be one table. Or, atleast, use a foreign key constraint. Joining both tables always forces a full scan since there is no reason for the optimizer to assume any shortcuts, which would be possible with foreign keys. Either merge the tables or introduce foreign key constraints.
The current imposed indices do not speed up queries, since there is no relation between the index on reinforcement_id and reinforcement. A foreign key constraint would impose such a relation.
The tables reinforcement_id and reinforcement are split and should be one table. Or, atleast, use a foreign key constraint. Joining both tables always forces a full scan since there is no reason for the optimizer to assume any shortcuts, which would be possible with foreign keys. Either merge the tables or introduce foreign key constraints.
The current imposed indices do not speed up queries, since there is no relation between the index on reinforcement_id and reinforcement. A foreign key constraint would impose such a relation.