Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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 (

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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

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.