Re: Displaying chat by punished users only to themselves (db fiddle attached)

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Alexander Farber <alexander(dot)farber(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Displaying chat by punished users only to themselves (db fiddle attached)
Date: 2022-05-04 15:28:24
Message-ID: CAKFQuwb7eFbS69BA+hkcA=Bz=MZcAQjhRTeZK899V=44+ymqpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, May 4, 2022 at 8:21 AM Alexander Farber <alexander(dot)farber(at)gmail(dot)com>
wrote:

> David, I am trying your suggestion:
>
> On Wed, May 4, 2022 at 4:27 PM David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> Assuming the base query is capable of returning all related chat messages
>> for both users (I'd probably place that portion into a CTE) the rows you
>> want to filter out are those whose c.uid is not my own, but only if their
>> muted property is true. It makes it easier to understand if you join
>> words_users twice, defining one as "them" and one as "me". Then you can
>> say something like: WHERE (c.uid = me.uid) OR NOT(them.muted)
>>
>>
>
You missed quoting the part where I describe the on clauses you need to
distinguish between "them" and "me"

Me: u.uid in (player...) and (s.uid = u.uid)
Them: u.uid in (player...) and (s.uid <> u.uid)

In particular, the IN expression causes two rows to be returned, one for
them and one for me - but for each join you only want one or the other.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Farber 2022-05-04 15:36:40 Re: Displaying chat by punished users only to themselves (db fiddle attached)
Previous Message Alexander Farber 2022-05-04 15:20:53 Re: Displaying chat by punished users only to themselves (db fiddle attached)