Provide environment information

  System:
    OS: Linux 6.5 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (12) x64 13th Gen Intel(R) Core(TM) i7-1355U
    Memory: 18.35 GB / 31.01 GB
    Container: Yes
    Shell: 3.7.1 - /usr/bin/fish
  Binaries:
    Node: 18.18.2 - ~/.local/share/nvm/v18.18.2/bin/node
    Yarn: 1.22.19 - ~/.local/share/nvm/v18.18.2/bin/yarn
    npm: 9.8.1 - ~/.local/share/nvm/v18.18.2/bin/npm
    pnpm: 8.10.5 - ~/.local/share/nvm/v18.18.2/bin/pnpm
    bun: 1.1.3 - ~/.bun/bin/bun

Describe the bug

using the auto-generated app with drizzle and postgres, when i create a post at 9:00 CEST (7:00 UTC), and inspect the database, the created_at timestamp actually shows 05:00:xx.xxxZ, so 2 hours before UTC. same thing for the updatedAt field (after adding api to update posts).

changing the drizzle data type to include timezone fixes the issue: timestamp("created_at", { withTimezone: true })

Reproduction repo

To reproduce

1. set up the app and run it
2. add a post
3. inspect the created_at timestamp, e.g. in drizzle studio

Additional information

No response