Question about interaction between migrations and model #58
Description
I have an existing database with about a dozen or so tables that I'm thinking of shifting to integrate with the TinyORM system.
I've read through the documentation about migrations and TinyORM, and want to get your take on what the next logical steps should be.
What I'd like to do is utilize the migrations mechanism to track database updates, while also having a model to interact with the database using ORM.
From what I can tell, you have to specify the full structure of the database using the model interface, but then at the same time expressing the migrations side separately.
My question is: Is there a way to map the migrations into the model? For example, if we have changes to a table, we would create a new migration to express those changes, then would we also have to update the model code as well? Or could the migration change update the model? I didn't see any mention of that interaction in the documentation, so I'm guessing they are meant to be independent?
Also, thank you for a great C++ tool for ORMs, hoping to get a chance to express the database using this library.