Replies: 1 comment 1 reply
-
Have you been able to resolve the issue? because I am also having the same issue. @donPuerto |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have the same problem with [Problem with migration (MySQL)]#1675](#1675).
/**
* "useTz: true" utilizes timezone option in PostgreSQL and MSSQL
*/
table.timestamp('expires_at', { useTz: true }).nullable()
table.timestamp('created_at', { useTz: true }).notNullable()
into
It should work.
It works on the migration however ``table.timestamps(true, true)

will only create
created_at` and `updated_at` not the expires_at column. See below imageSo, the result "ER_BAD_FIELD_ERROR: Unknown column 'expires_at' in 'field list'"

How do we resolve the issue?
To have
created_at
andexpires_at
Beta Was this translation helpful? Give feedback.
All reactions