postgresql/contrib/oracle/TODO

Add possible call to perl function for each field value exported
(data conversion on the fly before dump)

	- Fix problem regarding table/constraint output order.

The following need your help :

	- SQL queries converter.
	- PL/SQL code converter.
Update to new version of Oracle conversion utility, version 1.8. Gilles DAROLD 2002-04-04 00:55:57 -05:00			`Add possible call to perl function for each field value exported`
			`(data conversion on the fly before dump)`
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 2001-06-22 22:56:23 -04:00
Update to new version of Oracle conversion utility, version 1.8. Gilles DAROLD 2002-04-04 00:55:57 -05:00			`- Fix problem regarding table/constraint output order.`
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 2001-06-22 22:56:23 -04:00
			`The following need your help :`

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