#30677 [Asn->Csd]: Documentation of odbc_specialcolumns incorrect

ID: 30677 Updated by: mez@php.net Reported By: ian at rolfe dot com -Status: Assigned +Status: Closed Bug Type: Documentation problem Operating System: n/a PHP Version: Irrelevant Assigned To: mez New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: ------------------------------------------------------------------------ [2004-12-29 22:36:24] mez@php.net from Microsoft SQL_BEST_ROWID: Returns the optimal column or set of columns that, by retrieving values from the column or columns, allows any row in the specified table to be uniquely identified. A column can be either a pseudo-column specifically designed for this purpose (as in Oracle ROWID or Ingres TID) or the column or columns of any unique index for the table. SQL_ROWVER: Returns the column or columns in the specified table, if any, that are automatically updated by the data source when any value in the row is updated by any transaction (as in SQLBase ROWID or Sybase TIMESTAMP). I'll update this in a moment ------------------------------------------------------------------------ [2004-12-29 22:36:09] mez@php.net from Microsoft SQL_BEST_ROWID: Returns the optimal column or set of columns that, by retrieving values from the column or columns, allows any row in the specified table to be uniquely identified. A column can be either a pseudo-column specifically designed for this purpose (as in Oracle ROWID or Ingres TID) or the column or columns of any unique index for the table. SQL_ROWVER: Returns the column or columns in the specified table, if any, that are automatically updated by the data source when any value in the row is updated by any transaction (as in SQLBase ROWID or Sybase TIMESTAMP). I'll update this in a moment ------------------------------------------------------------------------ [2004-12-29 22:02:17] ian at rolfe dot com No, read it more carefully: for the type argument SQL_ROWVER the documentation says: "When the type argument is SQL_ROWVER, odbc_specialcolumns() returns the optimal column or set of columns that, by retrieving values from the column or columns, allows any row in the specified table to be uniquely identified. " This is pretty much the same as it says for SQL_BEST_ROWID, but the SQL_ROWVER and SQL_BEST_ROWID are distinctly different operations for this function. The ODBC driver documentation I have (and can be seen at microsoft.com amongst other places) defines the SQL_ROWVER operation as "columns that are automatically updated when any value in the row is updated by a transaction" which is not the same as the "optimal column or set of columns that, by retrieving values from the column or columns, allows any row in the specified table to be uniquely identified"! ------------------------------------------------------------------------ [2004-12-29 18:11:07] mez@php.net I think the Documentation says the same as you've just written, except for worded differently ------------------------------------------------------------------------ [2004-12-29 18:10:36] mez@php.net I think the Documentation says the same as you've just written, except for worded differently ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/30677 -- Edit this bug report at http://bugs.php.net/?id=30677&edit=1