Re: Oracle Style packages on postgres - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: Oracle Style packages on postgres
Date
Msg-id 20050511215944.GE31103@decibel.org
Whole thread Raw
In response to Re: Oracle Style packages on postgres  (elein@varlena.com (elein))
List pgsql-hackers
On Wed, May 11, 2005 at 02:41:43PM -0700, elein wrote:
> Adding to the ambiguity is the dot notation used for
> composite columns.  Don't forget the other end ignoring
> those required parens.
> 
> is foo.bar.zap 
>     a database.schema.table 
>     a schema.table.column
>     a table.column.column

Wouldn't that be handled by the FROM clause having to identify only
tables and views? Is there anyplace where dot notation actually extends
from database name down to columns? If that's the case, it seems
reasonable to me to require the use of table aliases in cases where
there's ambiguity.
-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Oracle Style packages on postgres
Next
From: Tom Lane
Date:
Subject: Re: Server instrumentation for 8.1