Kbase P176427: Is the ODBC statement attribute SQL_ATTR_CONCURRENCY supported through the Progress OpenEdge ODBC dr
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/29/2010 |
|
Status: Unverified
GOAL:
Is the ODBC statement attribute SQL_ATTR_CONCURRENCY supported through the Progress OpenEdge ODBC driver?
GOAL:
Is SQL_ATTR_CONCURRENCY supported by the Progress OpenEdge database?
GOAL:
Is SQL_ATTR_CONCURRENCY supported using the ODBC SQLSetStmtAttr and SQLGetStmtAttr functions?
GOAL:
Is SQL_ATTR_CONCURRENCY supported by the Progress OpenEdge RDBMS?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.2x
FIX:
The ODBC statement attribute SQL_ATTR_CONCURRENCY is supported through the Progress OpenEdge ODBC driver. This attribute is manipulated through the ODBC functions SQLSetStmtAttr and SQLGetStmtAttr. Its valid values are:
SQL_CONCUR_READ_ONLY = Cursor is read-only. No updates are allowed.
SQL_CONCUR_LOCK = Cursor uses the lowest level of locking sufficient to ensure that the row can be updated.
SQL_CONCUR_ROWVER = Cursor uses optimistic concurrency control, comparing row versions such as SQLBase ROWID or Sybase TIMESTAMP.
SQL_CONCUR_VALUES = Cursor uses optimistic concurrency control, comparing values.
The default value for SQL_ATTR_CONCURRENCY is SQL_CONCUR_READ_ONLY.