After adding a SQL constraint to a table, the table does not appear in the .df file when the definitions are dumped from the Data Administration tool
No feedback from Data Administration tool that table is not included in .df file
Behavior is the same even when the table with the SQL constraint is the only table dumped.

Enhancement Request# OE00205908

This is expected behavior: A table with a SQL constraint is excluded from a .df file created by the Data Administration tool "Dump Data Definitions" option in order to prevent SQL constraints from being lost when the definitions are loaded from that .df file.

SQL constraint definitions are not understood by ABL. If the Data Administration tool were to dump a .df for the table with the SQL constraint definition, the .df would not capture that constraint definition. Therefore, when the .df was loaded the new table definition would be lacking the SQL constraint definition.

Alternatively, if the SQLSCHEMA utility were used to dump and load the table definition, it would recreate the table including the SQL constraint definitions. However, SQLSCHEMA does not capture all of the ABL attributes such as Format, Validation expression, Description, etc.

Enhancement Request# OE00205908 has been logged for feedback from the Data Administration tool that such a table will not be included in the .df file when data definitions are dumped.

Defect OE00205909 has been logged to add a description of this behavior to the documentation.

The following procedure may be used to dump and load tables with existing SQL constraints:

The implementation mechanism for the SQL UNIQUE constraint is an ordinary index, which ABL does understand and enforce correctly. However, the SQL constraint definition per se is unknown to the ABL, so the table will still be excluded from the .df file when data definitions are dumped.

1. Use the SQLSCHEMA utility to dump the table definition. The constraints are dumped as ALTER TABLE statements.
2. Edit the ALTER TABLE statements produced by SQLSCHEMA to include only the constraints.
3. Drop the constraints using SQL Explorer.
4. Use the Data Administration tool to dump the table definition (.df file).
5. When it is time to reload the table:
   1. Load the table from the .df using the Data Administration tool.
   2. Load the constraints using SQLSCHEMA.

References to Written Documentation:

OpenEdge Data Management: Database Administration, "SQL Utilities > SQLSCHEMA utility"

OpenEdge Data Management: Database Administration, "Dumping and Loading"

Progress Article:

 Incremental.df dumps tables with SQL constraints