Table of Contents

Search

  1. Version 6.4.4
  2. Version 6.4.3 HotFix 1
  3. Version 6.4.3
  4. Version 6.4 HotFix 2
  5. Version 6.4 HotFix 1
  6. Version 6.4
  7. Version 6.3
  8. Version 6.2 Hot Fix 2
  9. Version 6.2 Hot Fix 1
  10. Version 6.2
  11. Version 6.1.1
  12. Version 6.1

Automatic Entity Generation

Automatic Entity Generation

The automatic entity generation component has the following changes:
  • If the tables in the entity have self-referential constraints, a warning message appears asking you to verify the constraints. If you continue to create the entity without changes to the constraints, the following limitations might apply:
    • You cannot validate the entity.
    • You can run the archive-only job. You cannot run the archive and purge job.
    • The archive-only job might archive a transaction more than one time.
    • After you archive the entity, you must delete the data from the source database.
    • If the archive job created duplicate records, you cannot restore the entity to the source database.
    Previously, if the tables in the entity had self-referential constraints, the entity creation component did not generate the correct insert and delete statements.
  • If the tables in the entity have multiple parents, a warning message appears asking you to verify the constraints. If you continue to create the entity without changes to the constraints, the following limitations might apply:
    • The archive job might archive a transaction more than one time. This occurs when multiple foreign keys point to the same parent table or the same record has multiple parent tables.
    • If multiple foreign keys point to same parent table, you must delete the data from the source database after you archive.
    • If the archive job created duplicate records, you cannot restore the entity to the source database.
    Previously, if the tables in the entity had multiple parents, the entity creation component did not generate the correct insert and delete statements.
  • In the SQL statement, the first time a table alias name appears, the table alias name is the same as the table name. For subsequent occurrences of the same table name, the automatic entity creation component generates the table alias name in the following format:
    AZ_<table ID>_<number of occurrence>
    . This format ensures that the table alias name is unique each time it occurs in the SQL statement. This format also prevents the table alias name from exceeding the maximum number of characters allowed by the database.
    Previously, the table alias name was
    <schema name>_<table name>
    regardless of the number of times it appeared in the SQL statement. The table alias name could exceed the maximum number of characters than that allowed by the database. Consequently, the archive job failed.
  • If the tables in the entity do not have constraints, a message appears letting you know that you must add a primary or unique key to create the entity.
    Previously, if the tables in an entity did not have constraints, the entity was created without the constraints. However, you could not save the entity unless you added the insert and delete statements.