Scenarios for table with constraints randomly fail

[HenrikPoulsen]

I am trying to use this package for some tables that have constraints.
I will randomly get constraint violations during LoadScenario().

This is because yaml.Unmarshal() does not preserve order by default. So it ends up returning the data in a different order than what is specified in the scenario. This can be resolved by using yaml.MapSlice which would preserve the order.

I don't know what the status of this project is. If you're open for accepting PRs I wouldn't mind spending some time on fixing this.

[till]

@HenrikPoulsen if you have a fix, I'd like to incorporate it into our fork :)

[HenrikPoulsen]

You can checkout my fork changes here
I got rid of the yaml logic and replaced it with go-migrate instead.
I have had no stability issues at all since I started using the changes in that fork