nodejs mssql date query returns long format date instead of default string literal
I have a sql query for a column which takes the value of 'date' when I run SELECT * FROM ConferenceMetaData
I get '2018-09-05'. The '2018-09-05' comes from the DB, but when I run the same SQL code in NodeJS the RecordSet returns "Tue Sep 04 2018 17:00:00 GMT-0700 (Pacific Daylight Time)".
Thus the question is: why am I not getting "2018-09-05" from running SELECT * FROM ConferenceMetaData
in NodeJS?
javascript node.js sql-server ssms
add a comment |
I have a sql query for a column which takes the value of 'date' when I run SELECT * FROM ConferenceMetaData
I get '2018-09-05'. The '2018-09-05' comes from the DB, but when I run the same SQL code in NodeJS the RecordSet returns "Tue Sep 04 2018 17:00:00 GMT-0700 (Pacific Daylight Time)".
Thus the question is: why am I not getting "2018-09-05" from running SELECT * FROM ConferenceMetaData
in NodeJS?
javascript node.js sql-server ssms
add a comment |
I have a sql query for a column which takes the value of 'date' when I run SELECT * FROM ConferenceMetaData
I get '2018-09-05'. The '2018-09-05' comes from the DB, but when I run the same SQL code in NodeJS the RecordSet returns "Tue Sep 04 2018 17:00:00 GMT-0700 (Pacific Daylight Time)".
Thus the question is: why am I not getting "2018-09-05" from running SELECT * FROM ConferenceMetaData
in NodeJS?
javascript node.js sql-server ssms
I have a sql query for a column which takes the value of 'date' when I run SELECT * FROM ConferenceMetaData
I get '2018-09-05'. The '2018-09-05' comes from the DB, but when I run the same SQL code in NodeJS the RecordSet returns "Tue Sep 04 2018 17:00:00 GMT-0700 (Pacific Daylight Time)".
Thus the question is: why am I not getting "2018-09-05" from running SELECT * FROM ConferenceMetaData
in NodeJS?
javascript node.js sql-server ssms
javascript node.js sql-server ssms
edited Nov 14 '18 at 1:58
Jack Giffin
1,051925
1,051925
asked Nov 13 '18 at 21:48
Deemal PatelDeemal Patel
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
nodeJS is interpreting the date returned from SQL Server as UTC date/time (2018-09-05 00:00:00) and it is converting that the current timezone, which assuming is PST/PDT would be 4th Sept @ 5pm.
So, the answer is that you ARE getting 2018-09-05 00:00:00 UTC, only it is being expressed in PST/PDT timezone. Try looking at the UTC value of the date object in nodeJS.
add a comment |
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%2f53290018%2fnodejs-mssql-date-query-returns-long-format-date-instead-of-default-string-liter%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
nodeJS is interpreting the date returned from SQL Server as UTC date/time (2018-09-05 00:00:00) and it is converting that the current timezone, which assuming is PST/PDT would be 4th Sept @ 5pm.
So, the answer is that you ARE getting 2018-09-05 00:00:00 UTC, only it is being expressed in PST/PDT timezone. Try looking at the UTC value of the date object in nodeJS.
add a comment |
nodeJS is interpreting the date returned from SQL Server as UTC date/time (2018-09-05 00:00:00) and it is converting that the current timezone, which assuming is PST/PDT would be 4th Sept @ 5pm.
So, the answer is that you ARE getting 2018-09-05 00:00:00 UTC, only it is being expressed in PST/PDT timezone. Try looking at the UTC value of the date object in nodeJS.
add a comment |
nodeJS is interpreting the date returned from SQL Server as UTC date/time (2018-09-05 00:00:00) and it is converting that the current timezone, which assuming is PST/PDT would be 4th Sept @ 5pm.
So, the answer is that you ARE getting 2018-09-05 00:00:00 UTC, only it is being expressed in PST/PDT timezone. Try looking at the UTC value of the date object in nodeJS.
nodeJS is interpreting the date returned from SQL Server as UTC date/time (2018-09-05 00:00:00) and it is converting that the current timezone, which assuming is PST/PDT would be 4th Sept @ 5pm.
So, the answer is that you ARE getting 2018-09-05 00:00:00 UTC, only it is being expressed in PST/PDT timezone. Try looking at the UTC value of the date object in nodeJS.
answered Nov 13 '18 at 22:02
AllumearzAllumearz
1896
1896
add a comment |
add a comment |
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%2f53290018%2fnodejs-mssql-date-query-returns-long-format-date-instead-of-default-string-liter%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