Robert Creager <[EMAIL PROTECTED]> writes:
> So the SELECT can manage this bot not the VIEW?
The spec constrains tables (and views) not to have duplicate column
names, but it does not say that about SELECT output lists.
regards, tom lane
---(end of
When grilled further on (Sun, 26 Jun 2005 15:18:47 -0400),
Tom Lane <[EMAIL PROTECTED]> confessed:
> Robert Creager <[EMAIL PROTECTED]> writes:
> > This doesn't seem right:
>
[ snip embarrassing mistake ]
>
> Why doesn't it seem right? You're asking it to generate a view with
> two columns both
Robert Creager <[EMAIL PROTECTED]> writes:
> This doesn't seem right:
> CREATE VIEW inci AS
> SELECT date, inci_id, protocol, a.ip_addr, b.ip_addr, spt, dpt
> FROM (SELECT addr_id, ip_addr FROM addrs) AS a
> JOIN incident ON incident.source_addr_id =3D a.addr_id=20
> JOIN (SELECT ad
This doesn't seem right:
CREATE VIEW inci AS
SELECT date, inci_id, protocol, a.ip_addr, b.ip_addr, spt, dpt
FROM (SELECT addr_id, ip_addr FROM addrs) AS a
JOIN incident ON incident.source_addr_id = a.addr_id
JOIN (SELECT addr_id, ip_addr FROM addrs)
AS b ON incident.de
