-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish migration #47
Comments
In general, yes, the usual |
The migration to create the table does not appeare in the migrations table.
When you do: migrate:refresh the table is not dropped and recreated.
It’s a bit annoying when your are refreshing often to have to manually clear the migrations_actions table
Phil
…On 13 Feb 2022, 22:02 +0000, Andrey Helldar ***@***.***>, wrote:
In general, yes, the usual copy operation. But why?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I understood what the problem is. At the moment, the mechanism of this package uses the mechanism of migrations with some changes. The peculiarity of migrations is that it does not create a table to create a table for storing migration statuses. In the near future I will add the ability to automatically create a migration table when executing the |
Have you tried |
@philipmclifton, I added a In case of rolling back migrations, the startup script can be one of the options: php artisan migrate:fresh
php artisan migrate:actions:fresh php artisan migrate:refresh
php artisan migrate:actions:fresh The |
Description:
Is it possible to publish the migration file?
The text was updated successfully, but these errors were encountered: