which gives me the same thing. but has different semantics so does different things in the presence of non-unique values. for some reason I thought it could do unexpected things when NULL values were involved, but a quick read suggests that's just NOT IN
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
bit late to the party! google pointed me to here and it seems interesting, hopefully I can get to the end...
given this is Postgres I'd use the
DISTINCT ON
operator, as it seems perfectly suited to the task:in this case you can also use an
IN
query:which gives me the same thing. but has different semantics so does different things in the presence of non-unique values. for some reason I thought it could do unexpected things when
NULL
values were involved, but a quick read suggests that's justNOT IN