Skip to Main Content
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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Under review
Workspace Informix
Components Informix Server
Created by Guest
Created on Jun 30, 2022

Enhancement to DROP PROCEDURE / DROP FUNCTION syntax

Currently, the DROP PROCEDURE statement requires that the all of the procedure parameters necessary to completely identify the specific procedure. This is important due to Informix supporting polymorphic procedures, and is generally a good thing.


However, it is a minor irritant that the syntax of the DROP PROCEDURE statement requires that only the argument datatypes be included between the parentheses, such as:

DROP PROCEDURE my_procedure(int, int, char, varchar);

When editing the source for a procedure, the CREATE PROCEDURE must have variable names in addition to the datatypes, such as:

CREATE PROCEDURE my_procedure( userid int, invoiceid int, name char(16), description varchar(255))


It would be a nice feature to be able to simply copy the CREATE PROCEDURE statement and change the first word from CREATE to DROP, and add the necessary trailing ';' character.

DROP PROCEDURE my_procedure( userid int, invoiceid int, name char(16), description varchar(255));


It should be a simple task to get the parser to ignore the variable names within the DROP PROCEDURE statement.


This is not a huge thing, but it is an ongoing annoyance to have to manually remove the variable names after copying the CREATE PROCEDURE. In some cases, it can be a couple of dozen parameters that have to be manually edited before the DROP can execute.

Needed By Not sure -- Just thought it was cool
  • Guest
    Jul 15, 2022

    Note: You can use my myschema utility to get DROP statements for any or all of your routines with the -drop option:

    $ myschema -d art -f all --drop-proc 2>/dev/null |fgrep DROP|head -10
    DROP FUNCTION "art".tabname ( );
    DROP FUNCTION "art".last_four ( CHAR(9) );
    DROP FUNCTION "informix".ssd_pr3 ( INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER );
    DROP FUNCTION "art".comment_in_the_middle ( INTEGER );
    DROP FUNCTION "art".comment_between ( INTEGER );
    DROP FUNCTION "art".runcondition ( );
    DROP FUNCTION "informix".sysbldsqltextin ( "informix".lvarchar(2048) );
    DROP FUNCTION "informix".sysbldsqltextout ( "informix".sysbldsqltext(24000) );
    DROP FUNCTION "informix".sysbldsqltextsend ( "informix".sysbldsqltext(24000) );
    DROP FUNCTION "informix".sysbldsqltextrecv ( "informix".sendrecv(2048) );

  • Guest
    Jul 12, 2022

    Hopefully there would be some way to restrict it so that this only works for functions/procedures created by the users, as opposed to those provided such as the assign*, binary18*, equal, notequal, etc.

  • Guest
    Jul 7, 2022

    We have been asking for this for years, it would be incredibly useful. I believe one of the rejection reasons in the past is it was too dangerous, what if some dropped all the 'assign' functions