Can I create a custom type which takes an id (NOT NULL) on INSERT but if not passed creates the id itself?

[205g0]

Means, if I pass .values({ id: generateId(), title: 'Hello World }) it takes the passed id, if I pass .values({ title: 'Hello World }) it generates id itself by calling generateId() in toDriver().

Problem: The type is NOT NULL on db level but optional on TS level, how can this be modeled?

[Senbonzakura1234]

Can we achieve this with raw SQL in the 1st place? If not then i don't think it's reasonable to add this feature, you should do it yourself by adding .catch after the promise, check the error code and rerun if it was duplicate id error

Also we should choose better random id system if this problem happen, instead of doing this, cuz the chance you run into this kind of error is nearly zero with nowadays random id technique

[205g0]

it's reasonable to add this feature

wasn't my question but how to achieve this with the current custom types (did you check them? great feature btw)

Also we should choose better random id system if this problem happen,

I create the generateId() myself. However, the q wasn't about random ids or whatever but...

• a column which is NOT NULL in MySQL but
• optional in TypeScript

and nothing else, still thanks for trying to help

[Senbonzakura1234]

it's reasonable to add this feature

wasn't my question but how to achieve this with the current custom types (did you check them? great feature btw)

Also we should choose better random id system if this problem happen,

I create the generateId() myself. However, the q wasn't about random ids or whatever but...

• a column which is NOT NULL in MySQL but
• optional in TypeScript

and nothing else, still thanks for trying to help

If so then i think the problem lies in the structure of your system itself, i assume the id col in your MySQL db is the primary key, so it was NOT NULL, if so the field you map to has to be not null also.
If you want a nullable id field then i suggest a second id field

[205g0]

the problem lies in the structure of your system itself,

No, this is a convenience feature some dbs offer, if the app does not provide the id, the db generates one for them (e.g. Mongo does this). And from a type perspective it's nothing bad either: Once data is written the id is required (NOT NULL) but not on app level. You can live without it but since Drizzle has so powerful custom types with hooks (toDriver and fromDriver), I thought about reimplementing this feature myself. Whatever, still thanks for trying to support.