Hi Ajit,
> -----Original Message-----
> From: ajit_cus [mailto:ajit_cus@;infosys.com]
[snip]
> The only statement concurrency currently being used is:
>
> ret = SQLSetStmtOption(m_stmt, SQL_CONCURRENCY, SQL_CONCUR_LOCK);
>
> I would like to continue to use this as this code is in a
> database provider to a third party application which works
> with other Databases too. Is SQL_CONCUR_LOCK not supported?
It is. The ODBC docu writes for this attribute:
Locking. The cursor uses the lowest level of locking necessary to make
sure it can update or delete rows in the result set. This usually results in
very low concurrency levels, especially at the Repeatable Read and
Serializable transaction isolation levels.
and
SQL_CONCUR_LOCK = Cursor uses the lowest level of locking
sufficient to ensure that the row can be updated.
So, if you do a "select count(*) from ..." you request a updatable result set.
> It is known to work with Oracle/db2/Sybase.
What did happen, if you try to update the result set (e.g. via SQLSetPos) of
the SQL statement above?
> Could someone confirm that Cursors under SAP DB ODBC are read only?
No, there can be updatable.
Regards Thomas
----------------------------------------------
Dr. Thomas K�tter
SAP DB, SAP Labs Berlin
SAP DB is open source. Get it! www.sapdb.org
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
