Should nullable columns always be optional? about sql-ts HOT 3 CLOSED

Thinking about it, you've convinced me.

Given the following different column null / default configurations.

NullableWithDefault
NullableWithoutDefault
NotNullableWithDefault 
NotNullableWithoutDefault

Should output the following

NullableWithDefault?: string | null
NullableWithoutDefault? : string | null
NotNullableWithDefault?: string
NotNullableWithoutDefault: string

Essentially null acts like a default and the only instance in which a column isn't optional is when it's not nullable and there's no default value.

I've gone through and updated all dialects to work as above, fixing a couple of bugs along the way. Hopefully be able to get it out within a day or so.

from sql-ts.

This is fixed in version 1.10.0. All clients have had their optionality and nullability standardised as per the above.

from sql-ts.

I agree that nullable columns should "default" to null without another explicit default. Omitting the value on insert in SQL would result in the value being null, and query builders like knex have the same interface.

from sql-ts.