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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.