A concrete example:
Following the Migrations section of the RW Tutorial, I initiated the command yarn rw prisma migrate dev Trying to answer the very first prompt Name of migration ... I failed to type the answer (“create posts”) because the terminal was for some reason solidly frozen (I am not going to chase the rathole to find the answer to why was it frozen)
So, I hit Ctrl-C to get the control from the terminal back - and while I did get it back, the generator proceeded ahead and created the migrations folder with content different from what I wanted.
Now, how to recover from this, not knowing what change the generator made to my code?. I cannot issue the yarn rw prisma migrate dev command again, as this will append a new migration to the already existing, unwanted one. Much less would I accept to start creating this app from scratch again, nor do I want to remove the migrations folder, hoping that this is the only thing I need to do in order to undo the initial yarn rw prisma migrate dev
The obvious solution is to ensure that all changes made by the interrupted generator are automatically removed by teaching the generators to use the transactional approach, a technique that Appolo supports.
Caveat: it is quite possible that I missed the fact that transactions are already being used 