3 ms·
I agree wildcards are better avoided but so are column orders in result extraction. They are a source of bugs and much review work when changes are made. If I
by GekkePrutser 6y ago
I agree wildcards are better avoided but so are column orders in result extraction. They are a source of bugs and much review work when changes are made.
If I had to choose (which usually isn't necessary) I'd say wildcards are the lesser evil.
- 867-5309 6y agoit's becoming increasingly more common to sort columns at the application layer
- rbut 6y agoI agree. Applications that rely on the ordering of columns are as bad as people who complain when I add a new column into, or change the ordering of a CSV which has column headers. There is no technical reason to do this; computers are ample fast enough to look up columns by name!
- csharptwdec19 6y ago>computers are ample fast enough to look up columns by name! Sure, but depending on number of records and/or implementation of the name lookup, it can add up over a large resultset, or have a slightly cost over many smaller queries. Mind you, I think -most- implementations are smart enough to only need to do the lookup once for a returned datareader, but the cost is still there.
- nkozyra 6y ago> so are column orders in result extraction. While I agree, there are some languages + db drivers where this is your only choice unless you roll your own. Go's sql package relies on order in the Scan method, for example.