Re: [GENERAL] Allowing SYSDATE to Work

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Matt Miller <pgsql(at)mattmillersf(dot)fastmail(dot)fm>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>
Subject: Re: [GENERAL] Allowing SYSDATE to Work
Date: 2006-11-19 22:37:53
Message-ID: 20061119223752.GA6436@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Josh Berkus wrote:
> Matt,
>
> > I now agree completely. My purpose is to migrate Oracle databases to
> > Posgres, and I had thought that Oracle didn't support CURRENT_DATE,
> > CURRENT_TIMESTAMP, and so on. However, I've just learned otherwise. So,
> > I think the proper migration process for a production database would be
> > to first change the Oracle DB to use CURRENT_DATE (or some other
> > standard psuedo column), since that will work properly under both Oracle
> > and Postgres.
>
> Yep, or use the Orafce project. We're happy to support compatibility syntax
> in completely separate add-in projects. Just not in the core code.

How does Orafce allow for grammar extensions like what would be needed
for SYSDATE to work? (Note no parens)

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2006-11-20 00:04:02 Re: phpPgAdmin, cannot connect to server
Previous Message dananrg 2006-11-19 22:05:02 Druid for postgreSQL - can I export my ERD to MS Access?

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2006-11-20 05:35:46 Re: [Fwd: Index Advisor]
Previous Message Joshua D. Drake 2006-11-19 20:29:23 Re: Nasty VACUUM/bgwriter/segmentation bug