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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

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.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On 11/19/06, Alvaro Herrera <alvherre@commandprompt.com> wrote:
> How does Orafce allow for grammar extensions like what would be needed
> for SYSDATE to work? (Note no parens)

IIRC, it doesn't handle SYSDATE as that would require a change to the grammar.

--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris@enterprisedb.com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On 11/18/06, Matt Miller <pgsql@mattmillersf.fastmail.fm> wrote:
>
> 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.
>

Correct approach. BTW, have you given EnterpriseDB a try?


--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | yahoo }.com

On Nov 21, 2006, at 10:59 AM, Matt Miller wrote:
>> BTW, have you given EnterpriseDB a try?
>
> I looked at it a year or more ago, but I decided it wasn't the type of
> approach I wanted. I want to focus on getting Oracle DBs migrated to
> Postgres proper. If I have to hack Postgres to ease the transition
> I'd
> rather do that than migrate to another commercial offering.
>
> Thanks for the reminder, though, I'll probably take another look, just
> to see what they're up to.

Well, EnterpriseDB supports both PostgreSQL and Oracle syntax, so it
does ease migration since you don't have to migrate every last piece
of code at once. It'd probably be worth your time to download it and
give it a try, but then again I'm biased.
--
Jim Nasby jim@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match