Cronix
Cronix
3 months ago (574,260 XP)

I really can't answer why it happened. If for some reason, after migrating, it didn't put the migration name in the migrations table, it would try to run it again the next time you migrated since it runs migrations that aren't in the migrations table. I used to mess up migrations too in the beginning when learning and doing things the wrong way, but haven't had that issue in years.

towhid

:) - thanks for your details but we have to find out why this problem occurred - may be- its cache problem @Cronix

Cronix
Cronix
3 months ago (574,260 XP)

It's impossible to know without precisely recreating all steps that led to the issue, and we can't do that unless you are able to reproduce the problem.

It wouldn't be cache related though. Migrations have nothing to do with cache.

towhid

ok :)

Please sign in or create an account to participate in this conversation.