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 Not under consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on Jun 27, 2022

More efficient unique indexes for monotonically increasing keys and constraints

Currently an index on a SERIAL and other monotonically increasing keys only add to the last node in the index causing the node to split into two half filled nodes. Eventually a sufficient number of nodes have so split that the index's search efficiency is reduced for finding more recent keys which are the most likely to be searched for.

I propose a new CREATE UNIQUE INDEX option, call it something like NOSPLIT, that causes the index logic to just add a new empty node without splitting the existing node. Such indexes might also default to FILLFACTOR 100 at create time rather than the ONCONFIG setting if a FILLFACTOR option is not present in the DDL.

Needed By Not sure -- Just thought it was cool
  • Admin
    Karen Qualley
    Jul 14, 2022

    After further discussions, it has been determined that these indexes are already more tightly packed than originally believed. Closing RFE as a result.