Same Issue !!!

Model definition

model Entity {
  ...
  createdAt            DateTime              @default(now()) @map("created_at")
  updatedAt            DateTime              @default(now()) @map("updated_at")
  ...
}

MySQL DDL

CREATE TABLE `entities` (
  ...
  `created_at` datetime(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
  `updated_at` datetime(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
  ...
);

DB rows

Returned by Prisma client

Prisma Version

...
"@prisma/client": "^5.13.0",
"prisma": "^5.13.0",
...

Edit

It turn's out there's no bug in the first place. I'm currently using Prisma in Remix and I totally forgot that the data I received on my component/frontend code actually crossed between server and client, hence, the datetime field on the server part (which is actually a native Date) gets serialized when received on frontend code.

I'm not so sure if that might also be the case for your @JoaoVitorLima242 .

from prisma.

Hi @drichardcarl.
Technicality, but Prisma does not return DateTime fields as strings, but rather, as JS Date objects which don't store the timezone. Non-UTC dates is one of the Prisma's weak spot which we are very well aware of and hope to fix one day.

If I understood correctly, in your case you always want to format the dates in GMT-3:00. If that's the case, result extension might provide some releif:

const prisma = new PrismaClient().$extends({
  result: {
    User: {
      createdAt: {
        needs: ['createdAt'],
        compute: (user) => formatInTheRightTimzone(user.createdAt)
      }
    }
  }
})

from prisma.