From: | "Jim Nasby" <jim(dot)nasby(at)enterprisedb(dot)com> |
---|---|
To: | "Matt Miller" <pgsql(at)mattmillersf(dot)fastmail(dot)fm> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Allowing SYSDATE to Work |
Date: | 2006-11-24 19:32:11 |
Message-ID: | 0B9BA73A-93FB-4139-B2BF-2245AB5BCF79@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Nov 17, 2006, at 4:26 PM, Matt Miller wrote:
> 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.
If you've got a lot of Oracle-specific code you might want to
consider using EnterpriseDB.
--
Jim Nasby jim(dot)nasby(at)enterprisedb(dot)com
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-11-24 19:47:25 | Re: COPY FROM encoding error |
Previous Message | Ron Johnson | 2006-11-24 19:14:16 | Re: indexes |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Kronuz | 2006-11-24 19:40:27 | Re: Various breakages in new contrib/isn module |
Previous Message | Andrew Sullivan | 2006-11-24 19:23:59 | Re: Integrating Replication into Core |