I'm importing data from older website to new one using database migrations. I have created first as one of first steps of development phase of new site. Then I planned to create another one, that will do final data import at the end of development process.
I was then faced with question, what will happen, if another import will be required a bit later?
Since (for many reasons) we cannot afford for a better solution (like a full installer, able to migrate current data at any point in time) and since such situation have small changes to arise and won't happen again. I suggested, that in this case we should copy import migration on top of all others and execute it once more.
In reply I was suggested, that I should rather create a recurring migration. I.e. the one, that updates migration table in database at the end of migration process, changes its own timestamp and thus forces migration system to "think", that there's always a new migration to be applied on top of all others.
I was a bit surprised with such suggestion. Is it wise and secure to create such thing?