On Tue, 15 Jul 2025, Laurenz Albe wrote:
Apart from that, the subquery seems to be missing a GROUP BY clause.
Laurenz,
That was added.
Thanks,
Rich
On Monday, July 14, 2025, Laurenz Albe wrote:
> On Mon, 2025-07-14 at 12:19 -0700, Rich Shepard wrote:
> > On Mon, 14 Jul 2025, David G. Johnston wrote:
> >
> > > The error indicates your script file is at least 127 lines long and you
> > > are showing like 9...also do you usually name your scrip
On Mon, 2025-07-14 at 12:19 -0700, Rich Shepard wrote:
> On Mon, 14 Jul 2025, David G. Johnston wrote:
>
> > The error indicates your script file is at least 127 lines long and you
> > are showing like 9...also do you usually name your script files with a
> > .txt extension?
>
> Agh! No the filen
On Mon, 14 Jul 2025, David G. Johnston wrote:
Yeah, you need both to read up on aggregate queries and correlated
subqueries which is typically how one makes uses of exists (it's called a
semi-join in this formulation)
David,
Thanks. I wasn't sure what to read.
Not tested, but:
select c.ind
On Mon, 14 Jul 2025, David G. Johnston wrote:
The error indicates your script file is at least 127 lines long and you
are showing like 9...also do you usually name your script files with a
.txt extension?
David J.,
Agh! No the filename extension is .sql. But I was using the \o psql option
to
