From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: death of array? |
Date: | 2017-04-07 15:57:22 |
Message-ID: | d1ce18b8-c5cb-9547-c0b3-8a4910f96483@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 04/07/2017 09:26 AM, David G. Johnston wrote:
> On Fri, Apr 7, 2017 at 8:22 AM, Rob Sargent <robjsargent(at)gmail(dot)com
> <mailto:robjsargent(at)gmail(dot)com>>wrote:
>
> Thank you both for your suggestions, but does either apply to
> joining through the array in a flow of join operations? Or must I
> do the work on the array in the where clause?
>
>
> field = any(array_col) works anywhere ...
>
> David J.
>
>
Understood but true if any match is found, I need every array member to
match as I want them all to be of a specific people as input into the
query (so field = all(array_col)) and "field" here would be
people_member.person_id and using that yields zero results in full query
(very quickly though).
But my understanding of the documentation of ALL is debatable. What
does "the left-hand expression is evaluated" yield for
people_member.person_id? The where clause would restrict it to one
people_id but thats still more that what's in probandset.probands.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-04-07 16:02:29 | Re: death of array? |
Previous Message | David G. Johnston | 2017-04-07 15:26:42 | Re: death of array? |