As it may be seen in Oban it is recommended to set up hard version on the initial migration, so we can ensure the ErrorTracker database matches the same schema over time.
This is important because other migrations may use our schema and if we do not specify it we may end up with the latest schema update (version 10 for example) when the next migration was expecting version 2.
As it may be seen in Oban it is recommended to set up hard version on the initial migration, so we can ensure the ErrorTracker database matches the same schema over time.
This is important because other migrations may use our schema and if we do not specify it we may end up with the latest schema update (version 10 for example) when the next migration was expecting version 2.