Tightening types on successful insert to not be `object | undefined`
When doing
I'm trying to do some seeding where I create some entries in one table and save them as variables, and then attempt to insert the IDs of those entries into another table as a foreign key that's non-nullable and TS tells me that they're potentially undefined, which is true.
Since this is seeding, I know I'm clearing my DB before this, so I know the inserts will succeed and that it's not an issue if they don't) so would the best way to silence these errors just be to add
more generally, I'm curious if there's a drizzle specific way to chain anything onto the
Is there something in the docs I'm missing, or alternatively has anybody written an extension method for
I know that this is basically the same as adding
after each insert, I was just curious if there's a better way.
db.insert(someTable).values(someValues).returning()object | undefinedI'm trying to do some seeding where I create some entries in one table and save them as variables, and then attempt to insert the IDs of those entries into another table as a foreign key that's non-nullable and TS tells me that they're potentially undefined, which is true.
Since this is seeding, I know I'm clearing my DB before this, so I know the inserts will succeed and that it's not an issue if they don't) so would the best way to silence these errors just be to add
!returnedObject!.idmore generally, I'm curious if there's a drizzle specific way to chain anything onto the
.values({...}).returning()undefinedonConflictDoNothingonConflictDoUpdateIs there something in the docs I'm missing, or alternatively has anybody written an extension method for
PgInsertBuilderconst [row] = await db.insert(table).values({}).returning().assertSuccess()rowI know that this is basically the same as adding
if (!row) throw new Error("failed to insert row")after each insert, I was just curious if there's a better way.
