Re:Selecting All Columns Except One in PostgreSQL
by anderse on Saturday May 19, 2018 @10:49AM
(#17108090)
Do you mean your database driver doesn’t supply you with field names, that you rely on order to map up data?
[ Parent
| on HN ]
Re:Selecting All Columns Except One in PostgreSQL
by tejasmanohar on Monday May 21, 2018 @06:01PM
(#17122232)
I guess I often rely on column order in Go, given Rows.Scan() [0]... so `select ` would be scary since someone may ALTER the table.
Maybe that's the antipattern! But it's also a feature so I feel like you're better off avoiding the . Also, if someone adds additional big columns, you may incur additional, unnecessary cost
Re:Selecting All Columns Except One in PostgreSQL
by scrollaway on Saturday May 19, 2018 @10:54AM
(#17108109)
Your driver can probably introspect, yes. You can also probably introspect yourself if you want to. But all this to be less explicit about what you're querying seems like a waste, doesn't it?