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
Created by Guest
Created on Apr 27, 2021

Connection pooling should not lock databases if all connections are closed

In case connection pooling is enabled in the driver (no matter if using ODBC, .NET Provider or the .NET Core provider), the driver keeps connections from the pool open to the database server in order for a faster reconnect in the applications.

Anyhow this has the drawback that if a database was selected during one of the operations and/or if an initial database is provided within the connection string, the connection to this database will be kept open by the driver even if all connection objects inside the program are closed and disposed.

Therefore a subsequent call with "DROP DATABASE" will fail with an error message by the server that the database is still in use (by that [stale] connections in the pool).

This makes automated unit testing using pooling impossible if you are using some kind of following procedure for the database:


b) load / insert initial set of data for the test

c) run tests on that (predefined) data


where d) is just to clean up the database server from any remains from the test run in case the tests were successfull.

Needed by Date Jun 1, 2021