Console updates datetime fields even when unchanged, causing timezone drift (+9h on every update)

[Kentaro-Furukawa]

👟 Reproduction steps

1. In Appwrite Console, go to Databases → your database → Tables.
2. Open a table that has a datetime column (e.g. startAt).
3. Create a row with startAt = 2026/01/01, 00:00:00.000 (Japan / UTC+9).
4. In the rows grid, click the three-dots menu (⋯) on the row and select Update.
5. Change another field (do NOT modify startAt) and click Update.
6. Observe that startAt has shifted by +9 hours.
7. Repeat update → datetime shifts by +9 hours every time.

👍 Expected behavior

It should preserve existing datetime values when a row is updated from the Console.

Datetime fields should not be modified unless the user explicitly edits them.
The Console should clearly indicate how datetime values are interpreted and saved.

👎 Actual Behavior

When a row is updated from the Console, datetime fields are re-submitted even if they were not modified.

The Console appears to send the datetime value displayed in local timezone and save it as UTC, which results in a +9 hour shift in Japan (UTC+9).

As a result, datetime values change on every update, even when the user does not edit them.

🎲 Appwrite version

Appwrite Cloud

💻 Operating system

MacOS

🧱 Your Environment

• Appwrite Cloud
• API Endpoint: https://sgp.cloud.appwrite.io/v1
• Browser: Google Chrome on macOS Version 143.0.7499.193 (Official Build) (arm64)
• Region: Japan (UTC+9)

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[Vamsi0702]

Hi, I'm a final-year B.Tech student currently contributing to the rtMedia ecosystem (specifically on security and data integrity). I've analyzed this timezone drift issue and I'd like to work on a fix for it. Could you please assign this to me? I am ready to set up the local Docker environment and start investigating the Console's datetime submission logic.