<p>The database will be storing the date as seconds since 1970 (epoch) and your view on that is not localised. However, the front end date is localised for your time zone.</p>

<p>Of this I am more sure than that the sun will rise tomorrow (thanks to a recent rise in right wing politicians).</p>

CC BY-SA 3.0
2017-06-01T13:15:53.137Z
That is an excellent suggestion, Jeremy.  I will dive into this to see if you are right.
John Stevens
CC BY-SA 3.0
2017-06-01T16:09:55.973Z
This answer is 100% correct. I recommend updating it to add more confidence. ;)
Lindsey D
CC BY-SA 3.0
2017-06-01T22:27:04.507Z
Hah - lol, done!
Jeremy Daalder
CC BY-SA 3.0
2017-06-09T19:04:08.953Z
Yes, it works perfect Jeremy :) I was out celebrating this solution, that's why I could not telling you before ;)
John Stevens
CC BY-SA 3.0
2017-06-01T10:50:22.747Z
2017-06-01T22:26:35.393Z
2017-06-01T22:26:35.393Z
Jeremy Daalder
<p>We just found out that in the database birthday field, all dates has 1-day difference than what is shown on the front-end. </p>

<p>On the front-end, it is the correct date by the way.</p>

<p>Question: Is it a bug and if not, why is this?</p>

<database><datetime><custom-field>
date in database -1 day as on frond-end
# date in database -1 day as on frond-end

(Asked by: username_0 on 2017-06-01)

We just found out that in the database birthday field, all dates has 1-day difference than what is shown on the front-end.

On the front-end, it is the correct date by the way.

Question: Is it a bug and if not, why is this?

**Tags:** database, datetime, custom-field


---

## 1 answers

### Answer by username_1 on 2017-06-01. Score: 4 | Accepted answer

The database will be storing the date as seconds since 1970 (epoch) and your view on that is not localised. However, the front end date is localised for your time zone.

Of this I am more sure than that the sun will rise tomorrow (thanks to a recent rise in right wing politicians).

> **Comments:**
> **username_0**: That is an excellent suggestion, Jeremy.  I will dive into this to see if you are right.  
> **username_2**: This answer is 100% correct. I recommend updating it to add more confidence. ;)  
> **username_1**: Hah - lol, done!  
> **username_0**: Yes, it works perfect Jeremy :) I was out celebrating this solution, that's why I could not telling you before ;)  

---

