Problem in migration MySQL #1313
-
https://cdn.discordapp.com/attachments/709554391807557876/735984569311952946/unknown.png |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 3 replies
-
Post the error here! |
Beta Was this translation helpful? Give feedback.
-
i sent link of image , which error is there |
Beta Was this translation helpful? Give feedback.
-
D:\Projects\Adonis V5 Projects Training\new_company>node ace migration:run
❯ migrating database\migrations\1587988332388_users |
Beta Was this translation helpful? Give feedback.
-
@ahmed2104 I am not sure how can you expect others to help you, when you are damn lazy in getting help
The better you describe your issues (with complete info), more are the chances of getting help |
Beta Was this translation helpful? Give feedback.
-
I ran into a similar issue. Mine happened when trying to run migrations against a MySQL 5.7 database in production. Not sure why this is happening but changing:
to
seemed to fix it for me. The error also came up for the auto-generated api_tokens migration as well. Changing:
to:
fixed the issue. Again this only happened in a MySQL 5.7 production environment. I think the issue has to do with time zone support on the MySQL version running. Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
Use |
Beta Was this translation helpful? Give feedback.
Use
table.timestamps(true, true)
instead oftable.timestamps(true)
in your migration.