'now()' as a value for DateTime fields since `new Date()` may be wrong

Problem

There is no reliable way to update a DateTime field to now(). @default(now()) only works for create. Assume the db runs on a server with a precise clock, but the query comes from another device (server, browser) whose clock you have no control over. If you use new Date() to update, it evaluates to this potentially wrong clock which is not in sync with the clock of the db. This may lead to broken invariants like time intervals that end (new Date()) before they start (now()).

Suggested solution

DateTime could also allow now() as a string literal to pass through to the db (or change to the db’s version of now()).

Alternatives

• executeRaw
• introduce a dummy field to update and rely on @updatedAt, see discussion below - seems like a hack/does not reflect intent.

Additional context

Example in discussion https://github.com/prisma/prisma/discussions/5582.

[leoyli-headsup]

Any update on this? I think it is fairly common that in most of situations we do want to take the server time as the client time is not trustable.

[zenhob]

I have an endpoint that start and stops a synchronized but low-resolution timer, and was surprised to see that Prisma doesn’t have a solution for this. Being able to use SQL now() in this context would be exceedingly helpful