Databases
StackOverflow2013
Postsdbo
POcorrect syntax required with 'ON DUPLICATE KEY UPDATE', SET option
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POcorrect syntax required with 'ON DUPLICATE KEY UPDATE', SET option
    primarykey
    data
    text
    <p>I have form.php in which a record is either created or edited. This page is called either by a a 'New Record' link, in which case there's no ID set, or by an 'EDIT' link in which case $_GET['ID'] is set (and used to retrieve the record).</p> <p>Plan A was: Submitting form.php to process.php; in process.php, if there's an ID, the query is an UPDATE, otherwise it's an INSERT. At one point this if/else was working as intended but refreshing created dupes so I began playing with 'ON DUPLICATE KEY UPDATE', however w/out success. Plan B eventually occurred to my tiny little brain: shouldn't process.php have only an INSERT query, with ON DUPLICATE KEY UPDATE added? Haven't got this working yet either.</p> <p>process.php:</p> <pre><code> &lt;?php // get $_POST from form.php *** note: no ID if it's a New Record *** $id = $_POST['ID']; $invNumber = $_POST['invoice-number']; $invDate = $_POST['invoice-date']; $projNumber = $_POST['project-number']; $client = $_POST['client']; $issueDate = $_POST['issue-date']; $task = $_POST['task']; $subTotal = $_POST['sub-total']; $tax = $_POST['tax']; $invTotal = $_POST['invoice-total']; $datePaid1 = $_POST['payment-date-1']; $datePaid2 = $_POST['payment-date-2']; $comments = $_POST['comments']; if (isset($_POST['submit'])) { $query = "INSERT INTO $table SET invNumber = '$invNumber', invDate = '$invDate', projNumber = '$projNumber', client = '$client', task = '$task', issueDate = '$issueDate', subTotal = '$subTotal', tax = '$tax', invTotal = '$invTotal', datePaid1 = '$datePaid1', datePaid2 = '$datePaid2', comments = '$comments' ON DUPLICATE KEY UPDATE invNumber = $invNumber, invDate = $invDate, projNumber = $projNumber, client = $client, task = $task, issueDate = $issueDate, subTotal = $subTotal, tax = $tax, invTotal = $invTotal, datePaid1 = $datePaid1, datePaid2 = $datePaid2 ID = LAST_INSERT_ID(ID) "; $lastID = mysql_insert_id(); $result = mysql_query($query) or die(mysql_error()); $affRows = mysql_affected_rows(); if (($result) &amp;&amp; ($affRows)) { echo "&lt;p class=\"status\"&gt; &lt;strong&gt;RECORD #".$id." UPDATED.&lt;/strong&gt;&lt;br /&gt; &lt;strong&gt;Records updated: " . $affRows . "&lt;/strong&gt; &lt;/p&gt;"; } // END if ($result ... } // END CASE 1 ?&gt; </code></pre> <p>Refreshing process.php INSERTs dupes whether there's an ID or not. My 'ID' column, btw, is primary key, unique index, auto-increment. So how does the $query check the ID before either INSERTing or UPDATEing?[enter pulling-hair-out cliché following days and nights of research and experimentation]</p> <p>Thanks in advance, s</p> <p>p.s. re: injection:</p> <p>I've been including this chunk in my head.php - pls let me know if this covers injection:</p> <pre><code>&lt;?php // prevent SQL Injection in $_POST variables: foreach ($_POST as $key =&gt; $value) { $_POST[$key] = mysql_real_escape_string($value); } // prevent SQL Injection in $_GET variables: foreach ($_GET as $key =&gt; $value) { $_GET[$key] = mysql_real_escape_string($value); } ?&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USshecky
    1. USshecky
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COYou can simplify your `ON DUPLICATE KEY UPDATE` clause by referencing `VALUES`. See http://stackoverflow.com/questions/302544/is-there-a-way-to-do-an-insert-on-duplicate-key-udpate-in-zend-framework/1207076#1207076
      singulars
      1. POcorrect syntax required with 'ON DUPLICATE KEY UPDATE', SET option
      1. This table or related slice is empty.
    2. COThanks Phoenix. I've been holding fast to the SET option because I find it easier to read. Based on what I've read to date, I'm unaware of any other advantage to using VALUES, unless it's the sole solution to my present problem. Cheers!
      singulars
      1. POcorrect syntax required with 'ON DUPLICATE KEY UPDATE', SET option
      1. USshecky
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload