Quote:
|
Originally Posted by stolze
Note that there are many other ways to connect to DB2. CLI is just one of them. Therefore, adjusting the CLI configuration is not a global change.
p.s: You should have a very good reason to use uncommitted read. Usually, such a change indicates a problem in your applications.
|
The DB2 Control Center uses the type 2 driver (I believe that is uses the CLI configuration?).
Unfortuneatley, the DB2 Control Center has a major flaw (introduced in recent releases). If you select data with a query and the "grid" is displayed with your result set, then if you place the cursor on one of the boxes in the grid, and then move the cursor to another box in the result set grid, then DB2 updates the row where your cursor originally was in the first grid (regardeless of whether or not the data was changed).
And worse, it does not autocommit, and holds an X lock on the row updated.
This is a major problem in many situations, for both development and produciton systems.