IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on May 13, 2013

Ability to re-create views and procedures without dependent objects being dropped

Some objects in a database often depend on other. As an example, if there is a view, another view can be built upon it.
Private and public synonyms can be created for those views, and permissions given to various users on those views.
If the first view needs to be recreated (change of code), it needs to be dropped and created again.
When it is dropped, all of the dependent objects are consequently dropped - the other view, all the related synonyms and permissions, and so on, recursively.
The DBA has no warning of it happening, and later has to guess or use any other complex method to conclude which objects were dropped
and has to recreate all of them.

What is needed is some kind of ALTER VIEW statement (or CREATE OR REPLACE), that will recreate only the view at hand, without dropping dependent objects.

There is a similar situation regarding stored procedures: recreating a procedure or function means all the permissions on it getting dropped.

In an environment with many database users where access control is implemented with views, private synonyms and stored procedures, ALTER VIEW and ALTER PROCEDURE would really cut a lot of DBA work.