Differences

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

--- v5:reference:connection:getinsertsql [2016/01/16 22:15] – ↷ Page moved from v5:reference:getinsertsql to v5:reference:connection:getinsertsql mnewnham
+++ v5:reference:connection:getinsertsql [2016/03/23 14:39] – [$recordSet] clarify usage of table name, reworded and reformat dregad
@@ Line 21: / Line 21: @@
 ===== Parameters =====
 ====  $recordSet ====
-The parameter ''$recordSet'' is either a recordset obtained by [[v5:reference:execute|executing]] a select statement to obtain an **empty recordset**. There is no need to read the row.
+The parameter ''$recordSet'' is either
-<code php>
+  * a //recordset// obtained by [[v5:reference:connection:execute|executing]] a select statement to obtain an **empty recordset**. There is no need to read the row. <code php>
 $SQL = "SELECT * FROM employees WHERE emp_no=-1";
 $result = $db->execute($SQL);
 $sql = $db->getInsertSql($result,.....
 </code>
-or
-<code php>
+  * a //string// specifying a table name <code php>
 $table = 'employees';
 $sql = $db->getInsertSql($table,....
-</code>
+</code> Note that in this case, due to the fact that the function passes the table name by reference, the following syntax is //not valid//: <code php>
-Note that in the second instance, because the function passes the table name by reference, the following syntax is not valid.
-<code php>
 /*
  * Incorrect syntax
  */
 $sql = $db->getInsertSql('employees',....
-</code>
+</code> Also note that this usage causes ADOdb to read the recordset information for itself, which may cause performance issues.
-Also note that in the second example, ADOdb must attempt to read the recordset information for itself, and there may be performance issues.
 ==== $fieldArray ====