Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / May 2006

Tip: Looking for answers? Try searching our database.

Moving cursor in Command Editor results screen results in update of table

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mark A - 27 Apr 2006 15:42 GMT
In the DB2 Admin Client (8.2.4), when the results of a query are displayed
in the grid that looks like a spreadsheet (using Command Editor or double
click on table name in Control Center). The data in this grid is updatable.

When a cursor is first placed on one of the columns, no update takes place.
When the cursor is then merely moved to another row (any column) the
previous row is updated, even if it was not changed. If the user does not
have authority to update the table, then a sqlcode -551 is displayed
indicating that they are authorized to update the table.

Is there any way let users query the data using these tools, and let them
move the cursor around without updating the data? This seems like a very
questionable design. There should be some way to let users just query the
data with tool without attempting updates just because they place the cursor
on a row in the grid.
Ian - 30 Apr 2006 21:58 GMT
> In the DB2 Admin Client (8.2.4), when the results of a query are displayed
> in the grid that looks like a spreadsheet (using Command Editor or double
[quoted text clipped - 11 lines]
> data with tool without attempting updates just because they place the cursor
> on a row in the grid.

To add to this, DB2 holds row locks -- so when the unsuspecting user
clicks on a row, they hold a lock on the row.  Or, if a select query
returns more than the "page limit" of the output (i.e. Command Editor
defaults to fetching 100 rows at a time, I think), DB2 will hold a
row lock for the current position of the cursor.

My experience has been that these situations always happens just before
the user leaves for lunch or some other extended absence, which wreaks
havoc for other users.
Mehmet Baserdem - 01 May 2006 17:38 GMT
Mark A,

One option is to create a schema which only has read privilege on the
tables and ask users to use this schema when they are querying the DB.

FYI: TXNISOLATION = 1 (i.e. Uncommitted Read) in db2cli.ini didn't work

Regards,

Mehmet
Mehmet Baserdem - 01 May 2006 17:43 GMT
read privilege => select privilege
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.