If I want to work with a date attribute as part of my model, would you suggest just storing it as a string or store it as a DateTime (I don’t need the time part)

Definitely DateTime! You should always try store data in their respective typed format. Maybe you don’t need it yet, but one day you might want to query/filter/sort/manipulate your data based on the date. So storing it as a proper date will give you access to a lot of convenient built-in functionalities.

@Sylvain (seel-vahn) In terms of inserting the data as a DateTime into my database. Do I need to convert the string date (since I receive as a string from the client json) into a

new Date

before I insert it?

I would store them as DateTime. Like what @Sylvain (seel-vahn) mentioned, you may don't need it for now but it will help you someday. A little story, in my company we have millions of data for date with string type in MongoDB because lack awareness of the design, and after years we need a feature which requires date filtering. We may change the date immediately but we can't do anything with the past data.

If I’m not mistaken, I think either would work - as Prisma client can accept both Javascript dates (using

new Date

) and strings (as long as they are following the ISO 8601 DateTime format).

@radisa Sounds like a nightmare I’d like to avoid. Thanks for the insight haha