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
Describe the bug
I'm re-creating an existing PostgreSQL database for my open-source project. I need to store small files, for which postgres uses the bytea data type. When looking into docs, the closes one we have is Binary, but it seems to try using a non-existent datatype for postgres when looking into the SQL output of masonite-orm migrate -s.
To Reproduce
Steps to reproduce the behavior:
Create migration with a binary filetype when using PostgreSQL database.
Execute or preview migration SQL to check the output
Expect to see PostgreSQL error 2021-04-11 21:49:07.609 UTC [530] ERROR: type "longblob" does not exist at character 109 during migration
Expected behavior
ORM should try to create the column with bytea data type.
Screenshots or code snippets
Screenshots help a lot. If applicable, add screenshots to help explain your problem.
Describe the bug
I'm re-creating an existing PostgreSQL database for my open-source project. I need to store small files, for which postgres uses the
bytea
data type. When looking into docs, the closes one we have is Binary, but it seems to try using a non-existent datatype for postgres when looking into the SQL output ofmasonite-orm migrate -s
.To Reproduce
Steps to reproduce the behavior:
2021-04-11 21:49:07.609 UTC [530] ERROR: type "longblob" does not exist at character 109
during migrationExpected behavior
ORM should try to create the column with
bytea
data type.Screenshots or code snippets
Screenshots help a lot. If applicable, add screenshots to help explain your problem.
What database are you using?
masonite-orm==1.0.45
The text was updated successfully, but these errors were encountered: