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 Not under consideration
Workspace Db2
Created by Guest
Created on Apr 3, 2019

Default of for read only for all select statements

As you might have noticed, the "for read only" clause of the select statement in DB2 is not widely known nor used. Most standards select statements going through the DB2 engine have the risk of becoming an ambiguous cursor with sub-optimal performance. In many cases the select won't benefit from blocking even though it's really just a normal select intended to just read data.

The following 2 changes will address this issue and will also be what developers and users intuitively want out of DB2.

1- Make the "for read only" clause to be the implicit default mode for all selects. No need to specify it explicitly.

2- Any select needed in a "For update" situation, the "For update" clause will need to be explicitly specified or the select/update will fail with an appropriate error message.

  • Guest
    May 8, 2019

    It's not possible to change the default as it would cause existing applications to fail.  While we could make it an optional default, it does not comply with the SQL standard, nor with the other Db2 family products.   Db2 already tries to determine the best option, if, for example, you select from a read-only view, FOR READ ONLY is implied.  It's not particularly onerous for developers to include FOR READ ONLY or FOR UPDATE as appropriate.