ID: 16187 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Documentation problem PHP Version: 4.1.2 New Comment:
I guess see what you're saying. The documentation kind of contradicts itself. Now, which part is wrong? Previous Comments: ------------------------------------------------------------------------ [2002-03-20 15:50:23] [EMAIL PROTECTED] Did you read the code at all? It is a documentation problem, not more, not less. How would the parameters to this function be useful, if only one of the possible constant values can be used? ------------------------------------------------------------------------ [2002-03-20 12:41:26] [EMAIL PROTECTED] The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php Anyway, it means you can use $object->field (with the fieldnames like in mysql_fetch_array) but not $object->1 (like in mysql_fetch_row). If you want more clarification to translate something correctly, ask it on [EMAIL PROTECTED] If you just want to know how it works, ask on [EMAIL PROTECTED] ------------------------------------------------------------------------ [2002-03-20 10:57:18] [EMAIL PROTECTED] <para> <function>mysql_fetch_object</function> is similar to <function>mysql_fetch_array</function>, with one difference - an object is returned, instead of an array. Indirectly, that means that you can only access the data by the field names, and not by their offsets (numbers are illegal property names). </para> <para> The optional argument <parameter>result_type</parameter> is a constant and can take the following values: MYSQL_ASSOC, MYSQL_NUM, and MYSQL_BOTH. See <function>mysql_fetch_array</function> for explanation of these constants. </para> Could someone please explain this? TIA, Manuzhai ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16187&edit=1
