As an API endpoint, I need to provide a table schema with a version number so that the mobile developers I am working with can cache the schema until it changes again.
I am automating this process, which complicates the "versioning" idea.
At first I thought that I could use the latest migration number as the version # but it occurred to me that Rails migrations are non-sequential now, so it would mean that I would need to give them all migration numbers and they would need to decide if there was a new migration present by comparing the arrays (maybe this is the solution?)
I’m wondering if I am missing anything - if there is any other schema version number in Rails apart from those stored in the migration table, or also if there was any way of tracking this through mysql.