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 (https://ideas.ibm.com).
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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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:
a) CREATE DATABASE
b) load / insert initial set of data for the test
c) run tests on that (predefined) data
d) DROP DATABASE
where d) is just to clean up the database server from any remains from the test run in case the tests were successfull.
Do not place IBM confidential, company confidential, or personal information into any field.