We have not seen this VEC issue re-occur, and there is little harm in adding a column index. The skills table is is used by resume-builder and so will live on for a while at least.
Verified that db:migrate is happy even if the index by the same name already exists, as is the case in production.
Fixes issue observed in production: https://github.com/department-of-veterans-affairs/devops/issues/873
We have not seen this VEC issue re-occur, and there is little harm in adding a column index. The skills table is is used by resume-builder and so will live on for a while at least.
Verified that db:migrate is happy even if the index by the same name already exists, as is the case in production.