php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #30677 Documentation of odbc_specialcolumns incorrect
Submitted: 2004-11-03 18:42 UTC Modified: 2004-12-29 22:42 UTC
From: ian at rolfe dot com Assigned: mez (profile)
Status: Closed Package: Documentation problem
PHP Version: Irrelevant OS: n/a
Private report: No CVE-ID: None
 [2004-11-03 18:42 UTC] ian at rolfe dot com
Description:
------------
There are a couple of problems with the documentation for odbc_specialcolumns

First, the type parameter:
* When the type argument is SQL_BEST_ROWID, 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. 
* When the type argument is SQL_ROWVER, odbc_specialcolumns() returns the
columns that are automatically updated when any value in the row is updated by a
transaction.

The "string qualifier" is the database name ("Catalogue" as referred to in other documentation).


Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2004-12-29 18:10 UTC] mez@php.net
I think the Documentation says the same as you've just written, except for worded differently
 [2004-12-29 18:11 UTC] mez@php.net
I think the Documentation says the same as you've just written, except for worded differently
 [2004-12-29 22:02 UTC] 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 22:36 UTC] 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 UTC] 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:42 UTC] mez@php.net
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.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed Sep 18 11:01:27 2024 UTC