You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following from #111, it is feasible for larger projects to have some manual intervention applied to the database over time. Especially feasible for old projects that are only recently adopting PhpGt/Database.
Rather than hard-coding a migration number to start from, a special flag could be passed that starts from a migration number but also resets the migration hashes before that point, in case they have become out of sync (possibly due to the database being exported/imported from backups on different servers).
The text was updated successfully, but these errors were encountered:
Following from #111, it is feasible for larger projects to have some manual intervention applied to the database over time. Especially feasible for old projects that are only recently adopting PhpGt/Database.
Rather than hard-coding a migration number to start from, a special flag could be passed that starts from a migration number but also resets the migration hashes before that point, in case they have become out of sync (possibly due to the database being exported/imported from backups on different servers).
The text was updated successfully, but these errors were encountered: