Allowing SYSDATE to Work - Mailing list pgsql-general

From Matt Miller
Subject Allowing SYSDATE to Work
Date
Msg-id 1163802397.5464.276316451@webmail.messagingengine.com
Whole thread Raw
Responses Re: Allowing SYSDATE to Work  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Allowing SYSDATE to Work  ("Jim Nasby" <jim.nasby@enterprisedb.com>)
List pgsql-general
I'd like SYSDATE to work syntactically and semantically the same as
CURRENT_TIMESTAMP (or CURRENT_TIME, or whatever).  I can create a
function called "sysdate" that does the trick, but then it seems I have
to reference the function as "sysdate ()," but I want to be able to get
away with just "sysdate."  It seems that CURRENT_TIMESTAMP and their
friends are magic functions that can be referenced without an explicit
empty argument list.

I have much Oracle-specific code that references sysdate, and porting
would be easier if that syntax could work unchanged in Postgres.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: can't delete because of constraint from zombie table
Next
From: Bob Pawley
Date:
Subject: After Update Triggers