 |
 |
Archives of the TeradataForum
Message Posted: Wed, 07 Jun 2000 @ 14:11:53 GMT
Subj: | | Re: LOCK ROW FOR WRITE in Bteq |
|
From: | | Roland Thomas |
How about, it doesn't matter what you use the RDBMS handles data integrity. It will lock a row hash or the table depending on what you
do. We update thousands of rows using hundreds of sessions and have never had a problem(knock on wood). The locking row option is almost
redundant but not quite. If you need to update a row in a specific order from input data you need to plan ahead but the RDBMS doesn't care,
it updates what it gets.
Comments?
| |