Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA42813 for ; Tue, 15 Feb 2000 22:03:24 -0500 (EST) (envelope-from Inoue@tpf.co.jp) Received: from cadzone ([126.0.1.40] (may be forged)) by sd.tpf.co.jp (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP id MAA02111; Wed, 16 Feb 2000 12:03:08 +0900 From: "Hiroshi Inoue" To: "Byron Nikolaidis" Cc: Subject: RE: [INTERFACES] Functions vs. Columns????? Date: Wed, 16 Feb 2000 12:09:17 +0900 Message-ID: <001001bf782b$35c6a180$2801007e@tpf.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <38AA04D4.4FDA646C@home.com> > -----Original Message----- > From: owner-pgsql-interfaces@postgreSQL.org > [mailto:owner-pgsql-interfaces@postgreSQL.org]On Behalf Of Byron > Nikolaidis > > Hi, > > I have a question as to how postgres handles some built-in functions, > for example: > > Works Doesn't Work > ------ ------------ > select now(); select now; > select current_date; select current_date(); > > 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. > > Any thoughts? > Parenthesis are needed in order to call functions in PostgreSQL. current_date isn't a built-in function of PostgreSQL. It's an SQL standard function and it's a special work of PostgreSQL parser to change current_date to call another built-in function. Regards. Hiroshi Inoue Inoue@tpf.co.jp