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
When running the introspect:pg command, some defaults are correctly wrapped in a sql tag while some others are not. To test this I have an almost untouched supabase instance running locally and also have multi schema set up in the drizzle config so that I can correctly pull in the auth schema since some of my tables are related to that auth.users table.
// bad default, should be wrapped in sql``exportconstusers=auth.table("users",{phone: text("phone").default(NULL::charactervarying),})// this one is rightexportconstworkspaces=pgTable("workspaces",{id: uuid("id").default(sql`uuid_generate_v4()`).primaryKey().notNull(),});
Same thing happens for some timestamp defaults.
Expected behavior
When running introspect, all defaults are correctly set or wrapped in the sql tag
What version of
drizzle-orm
are you using?0.29.1
What version of
drizzle-kit
are you using?0.20.6
Describe the Bug
When running the introspect:pg command, some defaults are correctly wrapped in a
sql
tag while some others are not. To test this I have an almost untouched supabase instance running locally and also have multi schema set up in the drizzle config so that I can correctly pull in the auth schema since some of my tables are related to thatauth.users
table.Same thing happens for some timestamp defaults.
Expected behavior
When running introspect, all defaults are correctly set or wrapped in the
sql
tagEnvironment & setup
The text was updated successfully, but these errors were encountered: