Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This answer is based on the assumption that you're using prepared statements</p> <p>If it's not the case, you should make the necessary adjustments.</p> <p>A. Collect the parameters inside an array</p> <pre><code>$params = array(':name' =&gt; 'foo', ':cat' =&gt; 'bar', ':val' =&gt; 'baz', [...]); </code></pre> <p>B. before calling <code>execute($params)</code>, do as follows, to register in a file the params you're using:</p> <pre><code>file_put_contents('file.log', implode(';', $params) . "\r\n"); //or "\n" on linux, "\r" on mac </code></pre> <p>C. call <code>execute($params)</code></p> <p>D. If the query is successful, GOTO A, otherwise, die.</p> <p>With this simple algorithm you'll have a logfile (named <code>file.log</code>) with all the parameters which have been successfully inserted plus the wrong ones (at the last row).</p> <p><strong>Possible improvement:</strong> </p> <p>This algorithm is not efficient, because you open and close the file multiple times. Follow these instructions instead if you care about efficiency:</p> <p>X. Define <code>$log = array();</code></p> <p>A. Collect the parameters inside an array</p> <pre><code>$params = array(':name' =&gt; 'foo', ':cat' =&gt; 'bar', ':val' =&gt; 'baz', [...]); </code></pre> <p>B. before calling <code>execute($params)</code>, do as follows, to store the params you're using:</p> <pre><code>$log[] = implode(';', $params) . "\r\n"; //or "\n" on linux, "\r" on mac </code></pre> <p>C. call <code>execute($params)</code></p> <p>D. If the query is successful, GOTO A, otherwise, <code>file_put_contents('file.log', implode("\r\n", $log));</code>.</p> <p><strong>Final consideration</strong></p> <p>Combine the above suggestion with the PDO exception that's raised by the error. Its stack is always very useful for debugging purposes.</p> <p>To enable exceptions with pdo, use this command after the connection:</p> <pre><code>$db-&gt;setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POError trapping within a large PDO sqlite transaction
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSTT LCU
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COAre you sure this will pick up deferred foreign key errors - as the keys are deferred they are only tested at the commit, not during the statement preparation. As you will see from my original post, I am using the PDO exception handling, but this does not provide detail of which part of the transaction failed, only the failure error (typically foreign key exception).
      singulars
      1. PO
      1. USAl.
    2. COYou should not use deferred foreign key errors, but instead enable them and insert your values in order to use correctly the foreign key relations. This way, you would be able to find who's breaking your script.
      singulars
      1. PO
      1. USSTT LCU
    3. COLOL if it were that simple... BTW it is not the errors that are deferred, but the validation - it is specifically for this case where you cannot be sure of supplying the foreign key inserts in the correct order.
      singulars
      1. PO
      1. USAl.
 

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