Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204])
	by hub.org (8.9.3/8.9.3) with ESMTP id AAA60506
	for <pgsql-interfaces@postgreSQL.org>;
	Wed, 16 Feb 2000 00:57:06 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id GAA11793;
	Wed, 16 Feb 2000 06:04:36 GMT
Sender: lockhart@hub.org
Message-ID: <38AA3DF4.A3AC0E00@alumni.caltech.edu>
Date: Wed, 16 Feb 2000 06:04:36 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Byron Nikolaidis <byron.nikolaidis@home.com>
CC: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Functions vs. Columns?????
References: <38AA04D4.4FDA646C@home.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> It seems that there should be some consistency here in the use of
> parenthesis.  I don't really know how these things are handled on the
> backend, but it seems that parenthesis are the more correct way, or at
> least both should be allowed.

The ones without parens are SQL-mandated "constants" which are
translated in the parser front end into function calls (usually with
some other name for historical reasons). Other function calls, like
now(), are really that: function calls.

> Any thoughts?

Uh, sure ;)

                     - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California