datetime object javascript save to MySQL
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have a really interesting problem that I'm fighting all day long so
my Techstack is ReactJS, NodeJS (Express) and MySQL. I try save datetime value in my MySQL and display this value in my ReactJS Application.
My problem:
When I generated new Data(), my object looked like this:
var date = new Date();
console.log(date);
Fri Jan 04 2019 01:23:10 GMT+0100 (czas środkowoeuropejski standardowy)
var json = JSON.stringify(date);
console.log(json);
"2019-01-04T00:23:10.525Z"
This object has been saved in the database as one hour too small. (2019-01-04 00:23:10) but when I displayed this object in my frontend, the hour was displayed correctly. (2019-01-04 01:23:10).
I would like to correctly save the time to the database and correctly display it in the application.
I've already found a solution to save the time to mysql correctly:
const x = new Date().getTimezoneOffset() * 60000;
const localISOTime = `${new Date(Date.now() - x)
.toISOString()
.slice(0, -1)}Z`;
...but I don't know, how to correctly display it on the application side.
I try use moment.js, but I don't know how to use it correctly.
javascript mysql datetime
asked Jan 4 at 0:31
ReactRouter4ReactRouter4
618
add a comment |
I have a really interesting problem that I'm fighting all day long so
my Techstack is ReactJS, NodeJS (Express) and MySQL. I try save datetime value in my MySQL and display this value in my ReactJS Application.
My problem:
When I generated new Data(), my object looked like this:
var date = new Date();
console.log(date);
Fri Jan 04 2019 01:23:10 GMT+0100 (czas środkowoeuropejski standardowy)
var json = JSON.stringify(date);
console.log(json);
"2019-01-04T00:23:10.525Z"
This object has been saved in the database as one hour too small. (2019-01-04 00:23:10) but when I displayed this object in my frontend, the hour was displayed correctly. (2019-01-04 01:23:10).
I would like to correctly save the time to the database and correctly display it in the application.
I've already found a solution to save the time to mysql correctly:
const x = new Date().getTimezoneOffset() * 60000;
const localISOTime = `${new Date(Date.now() - x)
.toISOString()
.slice(0, -1)}Z`;
...but I don't know, how to correctly display it on the application side.
I try use moment.js, but I don't know how to use it correctly.
javascript mysql datetime
asked Jan 4 at 0:31
ReactRouter4ReactRouter4
618
1
MySQL stores dates in UTC and converts them again on output. So if your timezone is not UTC, you will always see a difference in the stored value and the displayed value.
– Nick
Jan 4 at 0:36
1
You're doing this backwards. Your database should be holding the UTC time, not the local time. You can then convert to the UTC time back to local time on the client via something akin to.toLocaleString()
– Ben Beck
Jan 4 at 0:39
When I write:SELECT now()in MySQL, I have corectly result: 2019-01-04 01:23:10` so MySQL data time zone is set okay.
– ReactRouter4
Jan 4 at 0:53
add a comment |
I have a really interesting problem that I'm fighting all day long so
my Techstack is ReactJS, NodeJS (Express) and MySQL. I try save datetime value in my MySQL and display this value in my ReactJS Application.
My problem:
When I generated new Data(), my object looked like this:
var date = new Date();
console.log(date);
Fri Jan 04 2019 01:23:10 GMT+0100 (czas środkowoeuropejski standardowy)
var json = JSON.stringify(date);
console.log(json);
"2019-01-04T00:23:10.525Z"
This object has been saved in the database as one hour too small. (2019-01-04 00:23:10) but when I displayed this object in my frontend, the hour was displayed correctly. (2019-01-04 01:23:10).
I would like to correctly save the time to the database and correctly display it in the application.
I've already found a solution to save the time to mysql correctly:
const x = new Date().getTimezoneOffset() * 60000;
const localISOTime = `${new Date(Date.now() - x)
.toISOString()
.slice(0, -1)}Z`;
...but I don't know, how to correctly display it on the application side.
I try use moment.js, but I don't know how to use it correctly.
javascript mysql datetime
asked Jan 4 at 0:31
ReactRouter4ReactRouter4
618
I have a really interesting problem that I'm fighting all day long so
my Techstack is ReactJS, NodeJS (Express) and MySQL. I try save datetime value in my MySQL and display this value in my ReactJS Application.
My problem:
When I generated new Data(), my object looked like this:
var date = new Date();
console.log(date);
Fri Jan 04 2019 01:23:10 GMT+0100 (czas środkowoeuropejski standardowy)
var json = JSON.stringify(date);
console.log(json);
"2019-01-04T00:23:10.525Z"
This object has been saved in the database as one hour too small. (2019-01-04 00:23:10) but when I displayed this object in my frontend, the hour was displayed correctly. (2019-01-04 01:23:10).
I would like to correctly save the time to the database and correctly display it in the application.
I've already found a solution to save the time to mysql correctly:
const x = new Date().getTimezoneOffset() * 60000;
const localISOTime = `${new Date(Date.now() - x)
.toISOString()
.slice(0, -1)}Z`;
...but I don't know, how to correctly display it on the application side.
I try use moment.js, but I don't know how to use it correctly.
javascript mysql datetime
javascript mysql datetime
asked Jan 4 at 0:31
ReactRouter4ReactRouter4
618
asked Jan 4 at 0:31
ReactRouter4ReactRouter4
618
asked Jan 4 at 0:31
ReactRouter4ReactRouter4
618
asked Jan 4 at 0:31
ReactRouter4ReactRouter4
618
asked Jan 4 at 0:31
ReactRouter4ReactRouter4
618
618
1
MySQL stores dates in UTC and converts them again on output. So if your timezone is not UTC, you will always see a difference in the stored value and the displayed value.
– Nick
Jan 4 at 0:36
1
You're doing this backwards. Your database should be holding the UTC time, not the local time. You can then convert to the UTC time back to local time on the client via something akin to.toLocaleString()
– Ben Beck
Jan 4 at 0:39
When I write:SELECT now()in MySQL, I have corectly result: 2019-01-04 01:23:10` so MySQL data time zone is set okay.
– ReactRouter4
Jan 4 at 0:53
add a comment |
1
MySQL stores dates in UTC and converts them again on output. So if your timezone is not UTC, you will always see a difference in the stored value and the displayed value.
– Nick
Jan 4 at 0:36
1
You're doing this backwards. Your database should be holding the UTC time, not the local time. You can then convert to the UTC time back to local time on the client via something akin to.toLocaleString()
– Ben Beck
Jan 4 at 0:39
When I write:SELECT now()in MySQL, I have corectly result: 2019-01-04 01:23:10` so MySQL data time zone is set okay.
– ReactRouter4
Jan 4 at 0:53
1
1
MySQL stores dates in UTC and converts them again on output. So if your timezone is not UTC, you will always see a difference in the stored value and the displayed value.
– Nick
Jan 4 at 0:36
MySQL stores dates in UTC and converts them again on output. So if your timezone is not UTC, you will always see a difference in the stored value and the displayed value.
– Nick
Jan 4 at 0:36
1
1
You're doing this backwards. Your database should be holding the UTC time, not the local time. You can then convert to the UTC time back to local time on the client via something akin to
.toLocaleString()– Ben Beck
Jan 4 at 0:39
You're doing this backwards. Your database should be holding the UTC time, not the local time. You can then convert to the UTC time back to local time on the client via something akin to
.toLocaleString()– Ben Beck
Jan 4 at 0:39
When I write:
SELECT now() in MySQL, I have corectly result: 2019-01-04 01:23:10` so MySQL data time zone is set okay.– ReactRouter4
Jan 4 at 0:53
When I write:
SELECT now() in MySQL, I have corectly result: 2019-01-04 01:23:10` so MySQL data time zone is set okay.– ReactRouter4
Jan 4 at 0:53
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54031691%2fdatetime-object-javascript-save-to-mysql%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54031691%2fdatetime-object-javascript-save-to-mysql%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
MySQL stores dates in UTC and converts them again on output. So if your timezone is not UTC, you will always see a difference in the stored value and the displayed value.
– Nick
Jan 4 at 0:36
1
You're doing this backwards. Your database should be holding the UTC time, not the local time. You can then convert to the UTC time back to local time on the client via something akin to
.toLocaleString()– Ben Beck
Jan 4 at 0:39
When I write:
SELECT now()in MySQL, I have corectly result: 2019-01-04 01:23:10` so MySQL data time zone is set okay.– ReactRouter4
Jan 4 at 0:53