Kbase P187837: Table definitions missing in .df file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/31/2011 |
|
Status: Unverified
SYMPTOM(s):
Table definitions missing in .df file
Data Administration tool "Dump Data Definitions" does not dump tables with SQL Constraints
An incremental df against an empty database dumps all table definitions
Data Administration tool "Dump Data Definitions -> Create an incremental .df" option includes in the .df file any table that has a SQL constraint.
Once the table is loaded from the Data Administration tool, SQL constraints are lost.
No warnings when tables are not dumped to the .df
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
CAUSE:
The Data Administration tool "Dump Data Definitions -> Create an incremental .df" option should not include in the .df file any table that has a SQL constraint in order that SQL constraints are not lost when a table is dumped and loaded from the Data Administration tool.
SQL uniqueness constraint definitions, as definitions, are not understood by the ABL. The implementation mechanism for a uniqueness constraint is an ordinary index, which the ABL does understand and enforces correctly. But the "constraint definition" as a definition is unknown to the ABL.
By allowing the table to be dumped (through the 'incremental.df functionality) for the table with the SQL Constraint definition, the .df cannot capture the SQL constraint definition, just the index definition. When a table .df is then loaded from the Data Administration tool, SQL constraints are lost in the new table definition.
CAUSE:
Bug# OE00208080
FIX:
For further information to correctly dump and load Tables with SQL constraints,please refer to Solution P184392 "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"