We are using a set for the index changes on materialized views. A set is not ordered, which leads to the changes occasionally happening out of order. This is a problem when an index with the same name is being replaced as that has to happen in a particular order (drop first).
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
resolves #72
Problem
We are using a set for the index changes on materialized views. A set is not ordered, which leads to the changes occasionally happening out of order. This is a problem when an index with the same name is being replaced as that has to happen in a particular order (drop first).
Solution
Use a list instead of a set.
Checklist