Solve the problem of MongoDB storage time difference

When MongoDB stores the time type data, it is converted to UTC time, then stored in the database, and when we take out the stored time, there is the problem of jet lag. For example, we use the Beijing time, read the value will see the current time is less than 8 hours, it is said that each time we read a separate processing time, which is more troublesome. In fact, we can do the appropriate processing when storing, just use the getTimezoneOffset () and the toisostring () function.

getTimezoneOffset function: Returns the difference in this area (local time versus GMT Greenwich Mean Time) in minutes.

<script>  // 我们是东八区  var d = new Date();  var tz = d.getTimezoneOffset();  console.log(tz);  // -480</script>

Toisostring () function: Converts a Date object to a string using the ISO standard.

The standard is called ISO-8601, in the form of: Yyyy-mm-ddthh:mm:ss.sssz.

Package Time conversion function

localDate(v) {    const d = new Date(v || Date.now());    d.setMinutes(d.getMinutes() - d.getTimezoneOffset());    return d.toISOString();},

When we store time, we call Localdate (), which is the same, no matter what time zone you are in, the results show the same as local time.

Solve the problem of MongoDB storage time difference