# Time & DateTime fields recorded with an offset \[Mar 02\]

**URL:** <https://community.nocodb.com/t/time-datetime-fields-recorded-with-an-offset-mar-02/331>\
**Category:** Discord-Discussions\
**Created:** [November 3, 2022, 8:28am UTC](https://community.nocodb.com/t/time-datetime-fields-recorded-with-an-offset-mar-02/331 "2022-11-03T08:28:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![NocoDB](https://avatars.discourse-cdn.com/v4/letter/n/6f9a4e/32.png) [@NocoDB](https://community.nocodb.com/u/NocoDB)\
**Post date:** [November 3, 2022, 8:28am UTC](https://community.nocodb.com/t/time-datetime-fields-recorded-with-an-offset-mar-02/331/1 "2022-11-03T08:28:38Z")

</div>

> 🙋‍♂️ **ghost** _asked_

## One more bug, I am editing the `created_at` field, setting the time to 22:42 and when the dialog is closed, the time is set to 14:42 instead. EDIT: I checked the database structure, looks like the field type created for timestamps is without time zone. Maybe this is related, not sure.

---

<div class="post-metadata">

**Author:** ![NocoDB](https://avatars.discourse-cdn.com/v4/letter/n/6f9a4e/32.png) [@NocoDB](https://community.nocodb.com/u/NocoDB)\
**Post date:** [November 3, 2022, 8:28am UTC](https://community.nocodb.com/t/time-datetime-fields-recorded-with-an-offset-mar-02/331/2 "2022-11-03T08:28:39Z")

</div>

> 👨‍🦲 **dstala** _replied_

#### ghost@discord

#### Thank you for reporting this up. We have an issue in GIT for this. As you have rightly pointed out, it is associated with how we store/ handle timezone. Will keep you posted.

#

---

<div class="post-metadata">

**Author:** ![NocoDB](https://avatars.discourse-cdn.com/v4/letter/n/6f9a4e/32.png) [@NocoDB](https://community.nocodb.com/u/NocoDB)\
**Post date:** [November 3, 2022, 8:28am UTC](https://community.nocodb.com/t/time-datetime-fields-recorded-with-an-offset-mar-02/331/3 "2022-11-03T08:28:40Z")

</div>

[Autogenerated from discord](https://discord.com/channels/661905455894888490/948076094542712894)

* * *

#### Join [NocoDB’s](http://www.nocodb.com/) community

[Discord](https://discord.gg/5RgZmkW) • [Twitter](https://twitter.com/nocodb) • [Reddit](https://www.reddit.com/r/NocoDB/) • [Docs](https://docs.nocodb.com/)

---

<div class="post-metadata">

**Author:** ![Klappspatack](https://avatars.discourse-cdn.com/v4/letter/k/a587f6/32.png) [@Klappspatack](https://community.nocodb.com/u/Klappspatack)\
**Post date:** [May 26, 2023, 5:02am UTC](https://community.nocodb.com/t/time-datetime-fields-recorded-with-an-offset-mar-02/331/4 "2023-05-26T05:02:40Z")

</div>

I have a similar issue with the DateTime field  
I am running this on a vServer:

Node: **v16.19.1**  
Arch: **x64**  
Platform: **linux**  
Docker: **true**  
RootDB: **pg**  
PackageVersion: **0.107.4**

timezone on the vServer UTC+2  
timezone on my Laptop UTC+2

When I access NocoDB with the browser of my Laptop and I insert “2010-10-10 10:10” into the DateTime field and then press ‘reload’, the value automatically changes to “2010-10-10 12:10”

 ![Noco1](https://canada1.discourse-cdn.com/flex011/uploads/nocodb/original/1X/850ac44158ca380222d48b536992193f8b3bcb20.png)  
 ![Noco2](https://canada1.discourse-cdn.com/flex011/uploads/nocodb/original/1X/36009729465dcc2cd42bac135fadde4ccebf8ccd.png)

When I set the time zone of my Laptop to UTC, the inserted DateTime value doesn’t change.

So it looks as if the DateTime field would automatically add the timezone hours to the entry.  
I reproduced this with

-Firefox on Linux  
-Chrome on Linux  
-Firefox on Windows  
-Chrome on Windows

Unfortunately, this would make beautiful NocoDB unusable for my usercase.

---

<div class="post-metadata">

**Author:** ![Klappspatack](https://avatars.discourse-cdn.com/v4/letter/k/a587f6/32.png) [@Klappspatack](https://community.nocodb.com/u/Klappspatack)\
**Post date:** [June 15, 2023, 6:30am UTC](https://community.nocodb.com/t/time-datetime-fields-recorded-with-an-offset-mar-02/331/5 "2023-06-15T06:30:45Z")

</div>

With this installation, the ‘date’ and ‘datetime’ - fields work well without any adjustment of the system time zone:

Node: **v16.19.1**  
Arch: **x64**  
Platform: **linux**  
Docker: **true**  
RootDB: **pg**  
PackageVersion: **0.108.1**