DT
Drizzle Team•5mo ago
Zeraph

Why fields with default value is nullable

Consider this schema: 
export const blogMetadata = pgTable('blog_metadata', {
  id: varchar('id').primaryKey(),
  view: integer('view').default(0),
});
export const blogMetadata = pgTable('blog_metadata', {
  id: varchar('id').primaryKey(),
  view: integer('view').default(0),
});
When I do a query: 
db.select().from(blogMetadata).where(eq(blogMetadata.id, id))
db.select().from(blogMetadata).where(eq(blogMetadata.id, id))
The resultant type is: 
{
  id: string;
  view: number | null
}
{
  id: string;
  view: number | null
}
Why is view nullable in this case? It should always be an integer due to the default value of 0, isn't it? Or am I missing something?
2 Replies
piechart
piechart•5mo ago
You have to mark the column as NOT NULL. The default value is inserted if no value is provided, but you can still explicitly set a NULL value.
Zeraph
Zeraph•5mo ago
Thanks a lot for the explanation
Want results from more Discord servers?
Add your server
More Posts
[SQLite Expo driver] Error code : no such table: task_to_tags``` Error: Call to function 'NativeDatabase.prepareSync' has been rejected. → Caused by: Error code Missing module "pg-core" when attempting to push?Title says most of it. I can provide details, but I'm following the example pretty closely.Executing database migrations on Vercelnow planetscale is removing their free tier, i'm looking to move, which probably means i gotta use mIs there a way to set foreign key on a bulk insert?Apologies if this is a stupid question but I need to know if I'm missing something obvious. I have tonConflict or upsert?i have a table where email is a unique field. if im trying to insert into the table and the email isIf we're using Drizzlekit push, do we need to ever generate migrations?Is there anywhere I can explain what the migration scripts are for? When I push a change, can't we j