Differences

This shows you the differences between two versions of the page.

--- v5:reference:fetchobj [2016/01/15 01:33] – mnewnham
+++ v5:reference:recordset:fetchobj [2023/06/11 12:24] – fetchObj has no parameter dregad
@@ Line 1: / Line 1: @@
 ====== fetchObj =======
 ~~NOTOC~~
 <WRAP right box>
   obj fetchObj(
-      optional bool $upperCaseKeys=false
+      )
+  obj fetchObject(
+      optional bool $upperCaseKeys=true
       )
 </WRAP>
+====== fetchObject =======
 ===== Description =====
-The function ''fetchObj()'' returns the current row of a recordset as an ADOFetchObj object or false if past end-of-file and advances the pointer of the result. If the end-of-file is reached, the ''EOF'' attribute is set
+The ''fetchObj()'' / ''fetchObject()'' functions return the current row of a RecordSet as an ADOFetchObj object.
+They can be considered as aliases, except for the fact that ''fetchObject()'' converts the field names to uppercase by default, whereas ''fetchObj()'' does not.
+Unlike the [[v5:reference:recordset:fetchNextObj()]] method, the record pointer is not advanced. It is recommended that the 2 methods are not mixed in the same procedure.
+If the SQL statement results in an empty recordset or if the recordset has moved past end of file, then calling fetchObj() will return an empty record. Use [[v5:reference:connection:recordcount|recordCount()]] or check the EOF flag to ensure that you have retrieved a record.
 Results are influenced both by the [[v5:reference:adodb_assoc_case|ADODB_ASSOC_CASE]] constant and [[v5:reference:adodb_fetch_mode|$ADODB_FETCH_MODE]] attribute.
-The ADOFetchObj object has no special functionality, but the method is useful when the recordset data needs to be converted into e.g. JSON
+The ADOFetchObj object has no special functionality, but the method is useful when the recordset data needs to be converted into e.g. JSON.
 -------------------
 ===== Usage =====
@@ Line 41: / Line 57: @@
 */
 </code>
+{{tag>[PEAR Objects]}}