This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Generate drop of foreignkeys if foreignkey-statement is not provided
We generate DDL on the basis of an external tool and compare the newly generated DDL for each changed DB2 object against the catalog and let Admintool generate the conversion strategy as a workstatement list.
Whether an object has changed or not refers to the types database, tablespace, table, index, view etc., that means to every object that can be created independently.
Within these objects then all criteria, which are dependent, must be compared by the Admintool.
Related to tables this concerns e.g. the existence of columns, but also the existence of the foreignkey statement, because a foreignkey can never exist independently without the table.
If the foreignkey clause is not present in a create table statement, the foreignkey must therefore also be dropped.
Currently Admintool does not support this, but you have to either insert an explicit DropForeignkey - statement or bring the DDL of the parent table. However, since the DDL of the parent table does not have to have changed, it is not necessarily part of the input DDL.
To maintain compatibility with the current approach, the behavior we need could be controlled by a new, additional parameter, e.g. "suppress_drop_of_foreignkeys = 'N' ".
Do not place IBM confidential, company confidential, or personal information into any field.