pgsql/contrib/oracle CHANGES Ora2Pg.pm README. ...

From: Bruce Momjian - CVS <momjian(at)hub(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql/contrib/oracle CHANGES Ora2Pg.pm README. ...
Date: 2001-06-23 02:56:23
Message-ID: 200106230256.f5N2uNv86416@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

CVSROOT: /home/projects/pgsql/cvsroot
Module name: pgsql
Changes by: momjian(at)hub(dot)org 01/06/22 22:56:23

Modified files:
contrib/oracle : CHANGES Ora2Pg.pm README.ora2pg TODO
ora2pg.html ora2pg.pl

Log message:
Here the latest version and first working release of Ora2Pg a tool to export
Oracle database to PostgreSQL.

It currently dump the database schema (tables, views, sequences,
indexes, grants), with primary, unique and foreign keys into PostgreSQL
syntax without editing the SQL code generated. You can dump only a
particular schema from the Oracle database.

Functions, procedures and triggers with SQL or PLSQL code generated must
be reviewed to match the PostgreSQL syntax. Some usefull recommandation
on porting Oracle to PostgreSQL can be found at
http://techdocs.postgresql.org/
under the "Converting from other Databases to PostgreSQL" Oracle part. I
just
notice one thing more is that the trunc() function in Oracle is the same for
number
or date so be carefull when porting to PostgreSQL to use trunc() for number
and
date_trunc() for date.

I will add more precision in type NUMBER conversion based on length to match
as closest as possible all rich PostgreSQL numerics type. But it seems not to be

urgent as it seems that Oracle DBAs only create number with length 22 (default)
Space seems not to be their problem...

Gilles DAROLD

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian - CVS 2001-06-23 22:23:50 pgsql/src backend/parser/parse_coerce.c backen ...
Previous Message Bruce Momjian - CVS 2001-06-23 00:07:35 pgsql/ oc/src/sgml/ref/create_sequence.sgml rc ...