Migration Toolkit supports the migration of packages from an Oracle database into Advanced Server. See Section 3, Functionality Overview for information about the migration support offered by Advanced Server.Advanced Server does not currently support the enum data type, but will support them in future releases. Until then, you can use a check constraint to restrict the data added to an Advanced Server database. A check constraint defines a list of valid values that a column may take.The following code sample includes a simple example of a check constraint that restricts the value of a column to one of three dept types; sales, admin or technical.If we test the check constraint by entering a valid dept type, the INSERT statement works without error:If we try to insert a value not included in the constraint (support), Advanced Server throws an error:Postgres does not support materialized views compatible with Oracle databases. To setup a materialized view/summary table in Postgres you must manually create the triggers that maintain the summary table. Automatic query rewrite is not currently supported; the application must be made aware of the summary table's existence.When I try to migrate from a MySQL database that includes a TIME data type, I get the following error: Error Loading Data into Table: Bad format for Time. Does Postgres support MySQL TIME data types?Postgres will have no problem storing TIME data types as long as the value of the hour component is not greater than 24.Unlike Postgres, the MySQL TIME data type will allow you to store a value that represents either a TIME or an INTERVAL value. A value stored in a MySQL TIME column that represents an INTERVAL value could potentially be out of the accepted range of a valid Postgres TIMESTAMP value. If, during the migration process, Postgres encounters a value stored in a TIME data column that it perceives as out of range, it will return an error.