head	1.6;
access;
symbols
	REL7_4_29:1.5
	REL8_0_25:1.5
	REL8_1_21:1.5
	REL7_4_28:1.5
	REL8_0_24:1.5
	REL8_1_20:1.5
	REL7_4_27:1.5
	REL8_0_23:1.5
	REL8_1_19:1.5
	REL7_4_26:1.5
	REL8_0_22:1.5
	REL8_1_18:1.5
	REL7_4_25:1.5
	REL8_0_21:1.5
	REL8_1_17:1.5
	REL7_4_24:1.5
	REL8_0_20:1.5
	REL8_1_16:1.5
	REL7_4_23:1.5
	REL8_0_19:1.5
	REL8_1_15:1.5
	REL7_4_22:1.5
	REL8_0_18:1.5
	REL8_1_14:1.5
	REL7_4_21:1.5
	REL8_0_17:1.5
	REL8_1_13:1.5
	REL7_4_20:1.5
	REL8_0_16:1.5
	REL8_1_12:1.5
	REL7_3_21:1.3.2.2
	REL7_4_19:1.5
	REL8_0_15:1.5
	REL8_1_11:1.5
	REL7_3_20:1.3.2.2
	REL7_4_18:1.5
	REL8_0_14:1.5
	REL8_1_10:1.5
	REL7_3_19:1.3.2.2
	REL7_4_17:1.5
	REL8_0_13:1.5
	REL8_1_9:1.5
	REL8_0_12:1.5
	REL8_1_8:1.5
	REL7_3_18:1.3.2.2
	REL7_4_16:1.5
	REL8_0_11:1.5
	REL8_1_7:1.5
	REL8_0_10:1.5
	REL8_1_6:1.5
	REL7_4_15:1.5
	REL7_3_17:1.3.2.2
	REL8_1_5:1.5
	REL8_0_9:1.5
	REL7_4_14:1.5
	REL7_3_16:1.3.2.2
	REL7_3_15:1.3.2.2
	REL7_4_13:1.5
	REL8_0_8:1.5
	REL8_1_4:1.5
	REL7_3_14:1.3.2.2
	REL7_4_12:1.5
	REL8_0_7:1.5
	REL8_1_3:1.5
	REL7_3_13:1.3.2.2
	REL7_4_11:1.5
	REL8_0_6:1.5
	REL8_1_2:1.5
	REL7_3_12:1.3.2.2
	REL7_4_10:1.5
	REL8_0_5:1.5
	REL8_1_1:1.5
	REL8_1_STABLE:1.5.0.10
	REL8_1_0:1.5
	REL8_1_0RC1:1.5
	REL8_1_0BETA4:1.5
	REL8_1_0BETA3:1.5
	REL7_3_11:1.3.2.2
	REL7_4_9:1.5
	REL8_0_4:1.5
	REL8_1_0BETA2:1.5
	REL8_1_0BETA1:1.5
	REL7_2_8:1.2
	REL7_3_10:1.3.2.2
	REL7_4_8:1.5
	REL8_0_3:1.5
	REL8_0_2:1.5
	REL7_2_7:1.2
	REL7_3_9:1.3.2.2
	REL7_4_7:1.5
	REL8_0_1:1.5
	REL8_0_STABLE:1.5.0.8
	REL8_0_0:1.5.0.6
	REL8_0_0RC5:1.5
	REL8_0_0RC4:1.5
	REL8_0_0RC3:1.5
	REL8_0_0RC2:1.5
	REL8_0_0RC1:1.5
	REL8_0_0BETA5:1.5
	REL8_0_0BETA4:1.5
	REL7_4_6:1.5
	REL7_3_8:1.3.2.2
	REL7_2_6:1.2
	REL8_0_0BETA3:1.5
	REL8_0_0BETA2:1.5
	REL7_2_5:1.2
	REL7_4_5:1.5
	REL7_3_7:1.3.2.2
	REL7_4_4:1.5
	REL8_0_0BETA1:1.5
	REL7_4_3:1.5
	REL7_4_2:1.5
	REL7_3_6:1.3.2.2
	REL7_4_1:1.5
	REL7_3_5:1.3.2.2
	REL7_4:1.5
	REL7_4_RC2:1.5
	REL7_4_STABLE:1.5.0.4
	REL7_4_RC1:1.5
	REL7_4_BETA5:1.5
	REL7_4_BETA4:1.5
	REL7_4_BETA3:1.5
	REL7_4_BETA2:1.5
	WIN32_DEV:1.5.0.2
	REL7_4_BETA1:1.5
	REL7_3_4:1.3.2.2
	REL7_3_2:1.3.2.2
	REL7_2_4:1.2
	REL7_3_STABLE:1.3.0.2
	REL7_2_3:1.2
	REL7_2_STABLE:1.2.0.2
	REL7_2:1.2
	REL7_2_RC2:1.2
	REL7_2_RC1:1.2
	REL7_2_BETA5:1.2
	REL7_2_BETA4:1.2
	REL7_2_BETA3:1.2
	REL7_2_BETA2:1.2
	REL7_2_BETA1:1.2;
locks; strict;
comment	@# @;


1.6
date	2006.02.25.19.18.58;	author petere;	state dead;
branches;
next	1.5;

1.5
date	2003.01.07.22.17.14;	author momjian;	state Exp;
branches;
next	1.4;

1.4
date	2003.01.07.22.15.56;	author momjian;	state Exp;
branches;
next	1.3;

1.3
date	2002.04.04.05.55.57;	author momjian;	state Exp;
branches
	1.3.2.1;
next	1.2;

1.2
date	2001.06.23.02.56.23;	author momjian;	state Exp;
branches;
next	1.1;

1.1
date	2001.05.13.02.10.00;	author momjian;	state Exp;
branches;
next	;

1.3.2.1
date	2003.01.07.22.16.19;	author momjian;	state Exp;
branches;
next	1.3.2.2;

1.3.2.2
date	2003.01.07.22.17.23;	author momjian;	state Exp;
branches;
next	;


desc
@@


1.6
log
@Remove ora2pg; now available at <http://www.samse.fr/GPL/ora2pg/>.
@
text
@The following need your contribution :

	- SQL queries converter.
	- PL/SQL code converter.

@


1.5
log
@Upgrade to even newer ora2pg 2.0.
@
text
@@


1.4
log
@Upgrade to ora2pg 1.10.  Backpatch to 7.3.X.
@
text
@a2 1
	- Fix problem regarding table/constraint output order.
@


1.3
log
@Update to new version of Oracle conversion utility, version 1.8.

Gilles DAROLD
@
text
@d1 1
a1 2
Add possible call to perl function for each field value exported
(data conversion on the fly before dump)
a3 3

The following need your help :

@


1.3.2.1
log
@Upgrade to ora2pg 1.10.  Backpatch to 7.3.X.
@
text
@d1 2
a2 1
The following need your contribution :
d5 3
@


1.3.2.2
log
@Upgrade to even newer ora2pg 2.0.
@
text
@d3 1
@


1.2
log
@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
@
text
@d1 2
a2 1
Here are some more thing to do :
d4 1
a4 4
	- More precision in type conversion based on length
	  (I've no good DB to do that)

This will be done as soon as possible
a7 1
	- Extracting/converting datas.
@


1.1
log
@Update to ora2pg 1.2.
@
text
@d1 13
a13 6
- Extract sequences on tables. Seem to be difficult, can't find the way to link
  a sequence with one or more column. So problably just dump and edit manually
- More precision in type conversion based on length (I've no good DB to do that)
- Extract triggers and internal function.
- Extract datas.
- SQL queries converter.
@
