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.
Enabling Restrict on Drop clause logic in create table command for db2 LUW
There is a feature called "Restrict on Drop" that should be used by the database designers while creating a table for the db2 LUW database
1) If a database designer uses this "Restrict on Drop" clause for the creation of the table then the
tables does not get dropped
2) If a database designer does not use this clause "Restrict on Drop" clause during the creation of the table , then the tables gets dropped irrespective of whether the table has foreign keys and many more dependencies
So Say if the database designer opts for the second option and creates the tables in a database
and in future if he accidentally drops a table then the table gets dropped
Say if that table is referenced by around 10 tables again all thoese references are lost and also
all other dependencies on that table gets losted
So my point is why cant this logic of "Restrict on Drop" be embedded in the "Create table" Command itself so that by default the table goes into a state where it cannot be dropped
Do not place IBM confidential, company confidential, or personal information into any field.