fields with @updatedAt are not behaving as expected

[chrisdrackett]

1. Prisma version (prisma -v or npx prisma -v): 2.26.0

When using prisma studio and adding records with a field that has @updatedAt I expect the item to be added with the current dateTime as the value for updated at. Instead it is getting the value 1970-01-01T00:00:00.000Z

[sam3d]

Does this behaviour occur when seeding or interacting with the normal prisma client? I've been fixing this issue by setting the @updatedAt field to also have @default(now())

model User {
  id Int @id @default(autoincrement())
  createdAt DateTime @default(now())
  updatedAt DateTime @default(now()) @updatedAt
}

[chrisdrackett]

oh, this is probably worth trying!

[sdnts]

@chrisdrackett @sam3d That shouldn't be happening 🤔

Without Studio, you shouldn't need to add an explicit @default value to @updatedAt fields. Prisma Client should automatically handle @updatedAt field values on its own. If this isn't happening for you, you should definitely create an issue on https://github.com/prisma/prisma!

In Studio too, this is unexpected. I'll take a look!

[chrisdrackett]

I figured this was a studio but because from what I can tell this works as expected in prisma itself!

[chrisdrackett]

for example this is what I see when I press the Add Record button in studio:

[sdnts]

Ah okay, yeah that's a bug in Studio then. Will fix!

[sdnts]

This should be fixed in the latest dev version now (npm i prisma@dev @prisma.client@dev)! Fields that are marked as @updatedAt in your schema should now auto-populate with the current date & time. (If you already have a pending new record, you'll have to create a new one to observe this behaviour)

Do note that dev versions may contain unannounced breaking changes, so I wouldn't recommend using it in the long run for your app!
This will also make it to the next stable version of the Prisma CLI (Scheduled for July 27th). Let me know if this is still an issue!

[dashmug]

The variant of this bug still exists on Prisma 3.7.0.

When you click "Add Record", the updatedAt column is prepopulated by the time when you clicked that button.

As you edit the row and eventually save it, the row gets persisted in the DB but then the createdAt column (which is determined by the DB on write) will be later than the updatedAt.