News for hackers. Stuff that matters.
Re:SQL Anti-Patterns You Should Avoid by RHSeeger on Saturday October 18, 2025 @12:49PM (#45628665)
> Are there real-life cases where DISTINCT is the best choice by whatever metric you prioritize at the time

Indeed, along that line, I would say that DISTINCT can be used to convey intent... and doing that in code is important.

- I want to know the zipcodes we have customers in - DISTINCT

- I want to know how many customers we have in each zipcode - aggregates

Can you do the first with the second? Sure.. but the first makes it clear what your goal is.

Re:SQL Anti-Patterns You Should Avoid by dleeftink on Saturday October 18, 2025 @02:51PM (#45629559)
Partly in jest, but maybe we need a NON-DISTINCT signaller to convey the inverse and return duplicate values only.

SOMEWHAT-DISTINCT with a fuzzy threshold would also be useful.

Re:SQL Anti-Patterns You Should Avoid by RHSeeger on Saturday October 18, 2025 @05:03PM (#45630326)
I hear you. It's not all _that_ uncommon for me to query for "things with more than one instance". Although, to be fair, it's more common for me to that when grep/sort/uniqing logs on the command line.