Skip to Content
Sep 19, 2017 at 10:56 AM

What is the behavior of SELECT FOR UPDATE cursor?


Using SAP HANA 2 ODBC client, executing a cursor with SELECT FOR UPDATE, I want to compare the behavior with other database engines regarding concurrent data access when another client process does the same...

  1. Must be in a TX block? (does SELECT FOR UPDATE start a TX?)
  2. Lock granularity? (table level / data block / row / variable-granularity)?
  3. Release locks when cursor is closed?

Where can I find documentation about this?