Support Date only type

[rsktash]

Ability to pass date as 'YYYY-MM-DD'

[sanny-io]

I will look into this soon.

[sanny-io]

Actually, @rsktash are you able to use @db.Date ?

https://zenstack.dev/docs/reference/zmodel/attribute#native-type-mapping-attributes

[comman-fukui]

@sanny-io
@db.Date is mapped to the JavaScript Date type.
The Date type is affected by time zones, and when handling dates that do not include a time, it can cause unintended date discrepancies.
If @db.Date can be mapped to a “YYYY-MM-DD” string on the ORM side, this problem can be completely resolved.

[sanny-io]

@comman-fukui thank you, I see.

@ymc9 this is an interesting issue. I'm experimenting with an implementation of this that allows @db.Date to be used on String fields, but it introduces an incompatibility between ZenStack and Prisma schemas. I know compatibility is important. Recently, the format arg for ID functions had to be stripped from generated Prisma schemas because it caused errors.

That was fine because Prisma does not need to know about those args. However, this would be yet another incompatibility, but it would actually be more severe because you could not generate a Prisma schema at all 😅

What are your thoughts on this?

[sanny-io]

Actually, I just remembered that ZenStack uses Prisma for migrations, so that's a problem with @db.Date allowing String fields now. The goal is to eventually have both a native type mapping and string validation attribute. The string validation can be done now with no problem. #2689 is tracking this.

model User {
    ...
    birthdate String @db.Date @date
}