I can confirm that this is now fixed, and will appear in 7.1 when it is
released.
test=> select * from a natural inner join b natural inner join c;
a
---
1
(1 row)
> > > oh, btw this select refused to use an SQL natural join among the 3
> > > relations - the server gives up and disconnects w
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I can confirm this is still a bug.
Yeah, it's a parser problem. I punted it in Lockhart's direction, but
he's been out of town...
regards, tom lane
>> oh, btw this select refused to use an SQL natural join among the 3
>>>
I can confirm this is still a bug.
> > > oh, btw this select refused to use an SQL natural join among the 3
> > > relations - the server gives up and disconnects without warning.
> >
> > That sounds like a garden-variety bug. I'd be willing to look at it
> > if I had a complete example to foll
"Alexander H. Iliev" <[EMAIL PROTECTED]> writes:
> test=# select * from a natural inner join b natural inner join c;
> pqReadData() -- backend closed the channel unexpectedly.
Yup, I see it too. I had fixed some problems in SQL join syntax
since 7.0 release, but evidently not this one :-(. Will
> > oh, btw this select refused to use an SQL natural join among the 3
> > relations - the server gives up and disconnects without warning.
>
> That sounds like a garden-variety bug. I'd be willing to look at it
> if I had a complete example to follow, but I don't want to try to
> reverse-engine
"Alexander H. Iliev" <[EMAIL PROTECTED]> writes:
> does anyone have a clue what this diagnostic from psql (v 7.0) means:
> ERROR: aggregate function in qual must be argument of boolean operator
Aggregates and GROUP BY in views have a lot of restrictions at the
moment, and this is one of them: th
Hi all,
does anyone have a clue what this diagnostic from psql (v 7.0) means:
ERROR: aggregate function in qual must be argument of boolean operator
I got it from this query:
SELECT *
FROM last_payment NATURAL INNER JOIN admin_info
WHERE date_part ('month', age(last_payment.date, timestamp 'no
