You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.
In previous versions of Prisma we could pass this 2020-01-01 inside a resolver if we had a DateTime type and then use it to query items from database.
I'll provide an example of what I want to be able to do.
So suppose we have many different rows inside our table, which has a createdAt column. There is multiple rows which have the same date of creation but the time is different, like so 2020-01-01T21:00:00, 2020-01-01T00:00:00 and so on. If I'll pass 2020-01-01 I'll get all of those rows which have a 2020-01-01 as a date. Besides that it would be nice to be able to pass an array of dates like so [2020-01-01, 2020-01-02] and use it inside in parameter so it would return all of the rows within those days with all possible time values.
I hope this is a clear explanation. Would like to hear some comments on that.
The text was updated successfully, but these errors were encountered:
In previous versions of Prisma we could pass this
2020-01-01
inside a resolver if we had aDateTime
type and then use it to query items from database.I'll provide an example of what I want to be able to do.
So suppose we have many different rows inside our table, which has a
createdAt
column. There is multiple rows which have the same date of creation but the time is different, like so2020-01-01T21:00:00
,2020-01-01T00:00:00
and so on. If I'll pass2020-01-01
I'll get all of those rows which have a2020-01-01
as a date. Besides that it would be nice to be able to pass an array of dates like so [2020-01-01
,2020-01-02
] and use it insidein
parameter so it would return all of the rows within those days with all possible time values.I hope this is a clear explanation. Would like to hear some comments on that.
The text was updated successfully, but these errors were encountered: