Re:A Code Glitch May Have Caused Errors in More Than a Hundr...
by perl4ever on Saturday October 12, 2019 @03:39PM
(#21235671)
I mean, I have learned that people simply won't accept that SQL doesn't guarantee the order of a result set if you don't use "order by". I tried to argue it and eventually gave up. It seems vastly easier to change a language than human nature. People are hardwired to ignore claims that something should not be relied on, because in normal human relations, that is a way of pushing away undue responsibility, not something to be taken literally.
Re:A Code Glitch May Have Caused Errors in More Than a Hundr...
by bmc7505 on Saturday October 12, 2019 @05:09PM
(#21236346)
> A quick glance at the documentation didn't mention it
What do you mean? It is the very first sentence of the documentation: "results are returned in arbitrary order"
Re:A Code Glitch May Have Caused Errors in More Than a Hundr...
by luckylion on Saturday October 12, 2019 @05:34PM
(#21236514)
Ah, see, I missed that, I had just skimmed, then grepped for "sort" and "order" (but mistyped that as oder).
Re:A Code Glitch May Have Caused Errors in More Than a Hundr...
by magicbuzz on Saturday October 12, 2019 @03:35PM
(#21235656)
Most developers look at the result from a function call rather than looking at the documentation.
Re:A Code Glitch May Have Caused Errors in More Than a Hundr...
by emmelaich on Saturday October 12, 2019 @06:45PM
(#21236887)
It doesn't sort. But people assume it does especially if the files are returned in the order that they were created, which typically will be sorted.
I think this is why it doesn't get noticed; the files are written say
result-20190901-1303
result-20190901-1305
result-20190901-1310
etc...
A quick glance at the documentation didn't mention it, does glob even promise sorting the result? Relying on that to happen when it's not even promised seems negligent.