| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | "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>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: [GENERAL] Allowing SYSDATE to Work |
| Date: | 2006-11-18 23:34:31 |
| Message-ID: | 200611181534.31729.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
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.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Peterson | 2006-11-19 02:21:32 | composite type insert |
| Previous Message | Martijn van Oosterhout | 2006-11-18 22:15:07 | Re: User-defined-type in C crashing PostgreSQL server: What am I doing wrong? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Boreham | 2006-11-19 00:18:50 | Re: Ontology on PostgreSQL - is there something? |
| Previous Message | Josh Berkus | 2006-11-18 23:32:18 | Re: Ontology on PostgreSQL - is there something? |