Unparsed row in pg-promise when specifying SELECT columns
Why does pg-promise return a parsed object when querying with SELECT * ..., but returns an unparsed row when select columns are specified SELECT (given_name, family_name, photo) ...?
Select all columns:
db.oneOrNone(`SELECT * FROM $1~ WHERE id=$2`,[psql.tables.user, uid]);
> {"id":"1","given_name":"Michael","family_name":"Douglas","email":"mike.dougly@douglas.com","password":"9511393558AC7202E61EB7BA9A2D3FC1FA9CA151AFF4271C1475BD11A7BE5DC72DC8E0B2E8EA3D44DA476DB43728E1A2A4BCB08A63B2E724603B9EEBD268CE5A","birthdate":"1978-01-01T00:00:00.000Z","photo":"https://somefakewebsite.com/dougly.jpg"}
Select a subset of columns:
db.oneOrNone(`SELECT (given_name, family_name, photo) FROM $1~ WHERE id=$2`,[psql.tables.user, uid]);
> {"row":"(Michael,Douglas,https://somefakewebsite.com/dougly.jpg)"}
Is there a way to tell pg-promise to parse the column names like in the first case?
node.js postgresql pg-promise
asked Nov 27 '18 at 10:58
ezoritaezorita
8218
add a comment |
Why does pg-promise return a parsed object when querying with SELECT * ..., but returns an unparsed row when select columns are specified SELECT (given_name, family_name, photo) ...?
Select all columns:
db.oneOrNone(`SELECT * FROM $1~ WHERE id=$2`,[psql.tables.user, uid]);
> {"id":"1","given_name":"Michael","family_name":"Douglas","email":"mike.dougly@douglas.com","password":"9511393558AC7202E61EB7BA9A2D3FC1FA9CA151AFF4271C1475BD11A7BE5DC72DC8E0B2E8EA3D44DA476DB43728E1A2A4BCB08A63B2E724603B9EEBD268CE5A","birthdate":"1978-01-01T00:00:00.000Z","photo":"https://somefakewebsite.com/dougly.jpg"}
Select a subset of columns:
db.oneOrNone(`SELECT (given_name, family_name, photo) FROM $1~ WHERE id=$2`,[psql.tables.user, uid]);
> {"row":"(Michael,Douglas,https://somefakewebsite.com/dougly.jpg)"}
Is there a way to tell pg-promise to parse the column names like in the first case?
node.js postgresql pg-promise
asked Nov 27 '18 at 10:58
ezoritaezorita
8218
add a comment |
Why does pg-promise return a parsed object when querying with SELECT * ..., but returns an unparsed row when select columns are specified SELECT (given_name, family_name, photo) ...?
Select all columns:
db.oneOrNone(`SELECT * FROM $1~ WHERE id=$2`,[psql.tables.user, uid]);
> {"id":"1","given_name":"Michael","family_name":"Douglas","email":"mike.dougly@douglas.com","password":"9511393558AC7202E61EB7BA9A2D3FC1FA9CA151AFF4271C1475BD11A7BE5DC72DC8E0B2E8EA3D44DA476DB43728E1A2A4BCB08A63B2E724603B9EEBD268CE5A","birthdate":"1978-01-01T00:00:00.000Z","photo":"https://somefakewebsite.com/dougly.jpg"}
Select a subset of columns:
db.oneOrNone(`SELECT (given_name, family_name, photo) FROM $1~ WHERE id=$2`,[psql.tables.user, uid]);
> {"row":"(Michael,Douglas,https://somefakewebsite.com/dougly.jpg)"}
Is there a way to tell pg-promise to parse the column names like in the first case?
node.js postgresql pg-promise
asked Nov 27 '18 at 10:58
ezoritaezorita
8218
Why does pg-promise return a parsed object when querying with SELECT * ..., but returns an unparsed row when select columns are specified SELECT (given_name, family_name, photo) ...?
Select all columns:
db.oneOrNone(`SELECT * FROM $1~ WHERE id=$2`,[psql.tables.user, uid]);
> {"id":"1","given_name":"Michael","family_name":"Douglas","email":"mike.dougly@douglas.com","password":"9511393558AC7202E61EB7BA9A2D3FC1FA9CA151AFF4271C1475BD11A7BE5DC72DC8E0B2E8EA3D44DA476DB43728E1A2A4BCB08A63B2E724603B9EEBD268CE5A","birthdate":"1978-01-01T00:00:00.000Z","photo":"https://somefakewebsite.com/dougly.jpg"}
Select a subset of columns:
db.oneOrNone(`SELECT (given_name, family_name, photo) FROM $1~ WHERE id=$2`,[psql.tables.user, uid]);
> {"row":"(Michael,Douglas,https://somefakewebsite.com/dougly.jpg)"}
Is there a way to tell pg-promise to parse the column names like in the first case?
node.js postgresql pg-promise
node.js postgresql pg-promise
asked Nov 27 '18 at 10:58
ezoritaezorita
8218
asked Nov 27 '18 at 10:58
ezoritaezorita
8218
asked Nov 27 '18 at 10:58
ezoritaezorita
8218
asked Nov 27 '18 at 10:58
ezoritaezorita
8218
asked Nov 27 '18 at 10:58
ezoritaezorita
8218
8218
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
...returns an unparsed row when select columns are specified
You do not just specify columns, you place them into parenthesis, which tells PostgreSQL to return tuples, which is what you are getting. And if you run your query in pgAdmin, you will see the same.
Is there a way to tell pg-promise to parse the column names like in the first case?
Remove the parenthesis, and that's it.
answered Nov 27 '18 at 13:55
vitaly-tvitaly-t
11.1k34771
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%2f53498157%2funparsed-row-in-pg-promise-when-specifying-select-columns%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
...returns an unparsed row when select columns are specified
You do not just specify columns, you place them into parenthesis, which tells PostgreSQL to return tuples, which is what you are getting. And if you run your query in pgAdmin, you will see the same.
Is there a way to tell pg-promise to parse the column names like in the first case?
Remove the parenthesis, and that's it.
answered Nov 27 '18 at 13:55
vitaly-tvitaly-t
11.1k34771
add a comment |
...returns an unparsed row when select columns are specified
You do not just specify columns, you place them into parenthesis, which tells PostgreSQL to return tuples, which is what you are getting. And if you run your query in pgAdmin, you will see the same.
Is there a way to tell pg-promise to parse the column names like in the first case?
Remove the parenthesis, and that's it.
answered Nov 27 '18 at 13:55
vitaly-tvitaly-t
11.1k34771
add a comment |
...returns an unparsed row when select columns are specified
You do not just specify columns, you place them into parenthesis, which tells PostgreSQL to return tuples, which is what you are getting. And if you run your query in pgAdmin, you will see the same.
Is there a way to tell pg-promise to parse the column names like in the first case?
Remove the parenthesis, and that's it.
answered Nov 27 '18 at 13:55
vitaly-tvitaly-t
11.1k34771
...returns an unparsed row when select columns are specified
You do not just specify columns, you place them into parenthesis, which tells PostgreSQL to return tuples, which is what you are getting. And if you run your query in pgAdmin, you will see the same.
Is there a way to tell pg-promise to parse the column names like in the first case?
Remove the parenthesis, and that's it.
answered Nov 27 '18 at 13:55
vitaly-tvitaly-t
11.1k34771
answered Nov 27 '18 at 13:55
vitaly-tvitaly-t
11.1k34771
answered Nov 27 '18 at 13:55
vitaly-tvitaly-t
11.1k34771
answered Nov 27 '18 at 13:55
vitaly-tvitaly-t
11.1k34771
11.1k34771
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%2f53498157%2funparsed-row-in-pg-promise-when-specifying-select-columns%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
