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
I have verified that the bug I'm about to report hasn't been filed before.
What version of drizzle-orm are you using?
0.36.1
What version of drizzle-kit are you using?
0.28.0
Other packages
No response
Describe the Bug
Hello, I have encountered an issue concerning type generation. When a schema is updated, After updating a schema and running the commands npx drizzle-kit generate and npx drizzle-kit migrate, the newly added fields are not recognized in the code, even after restarting the TypeScript server in VSCode.
Schema:
Error:
Database have been successfully updated:
With this being said, there is no problem with migration using drizzle-kit, but new types are not being generated automatically.
I tried deleting drizzle folder and creating the migrations again, but this also did not work.
The text was updated successfully, but these errors were encountered:
NimaCodez
changed the title
[BUG]: Types of updated schemas is not been generated after migration
[BUG]: Types of updated schemas are not been generated after migration
Dec 31, 2024
Report hasn't been filed before.
What version of
drizzle-orm
are you using?0.36.1
What version of
drizzle-kit
are you using?0.28.0
Other packages
No response
Describe the Bug
Hello, I have encountered an issue concerning type generation. When a schema is updated, After updating a schema and running the commands
npx drizzle-kit generate
andnpx drizzle-kit migrate
, the newly added fields are not recognized in the code, even after restarting the TypeScript server in VSCode.Schema:
Error:
Database have been successfully updated:
With this being said, there is no problem with migration using drizzle-kit, but new types are not being generated automatically.
I tried deleting drizzle folder and creating the migrations again, but this also did not work.
The text was updated successfully, but these errors were encountered: