Databases
StackOverflow2013
Postsdbo
POIs it OK to allow sometimes dynamic SQL without sanitization?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs it OK to allow sometimes dynamic SQL without sanitization?
    primarykey
    data
    text
    <p>My partner on a PHP project objects my practice of always sanitizing integer values in dynamic SQL. We do use parameterized queries when possible. But for UPDATE and DELETE conditions <code>Zend_Db_Adapter</code> requires a non-parameterized SQL string. That's why I, even without thinking, always write something like:</p> <pre><code>$db-&gt;delete('table_foo', 'id = ' . intval($obj-&gt;get_id())); </code></pre> <p>Which is equivalent, but is a shorter version of (I've checked the ZF source code):</p> <pre><code>$db-&gt;delete('table_foo', $db-&gt;qouteInto('id = ?', $obj-&gt;get_id(), 'INTEGER')); </code></pre> <p>My partner strongly objects this <code>intval()</code>, saying that if <code>$obj</code> ID is null (the object is not yet saved to DB), I will not notice an error, and the DB operation will just silently execute. That's what has actually happened to him.</p> <p>He says that if we sanitize all the HTML forms input, there's no way an integer ID can possibly get into <code>'; DROP TABLE ...'</code>, or <code>' OR 1 = 1</code>', or another nasty value, and get inserted into our SQL queries. Thus, I'm just paranoid, and am making our lives unnecessarily more complicated. "Stop trusting the <code>$_SESSION</code> values then" he says.</p> <p>However, for string value conditions he does agree with:</p> <pre><code>$db-&gt;update-&gt;( 'table_foo', $columns, 'string_column_bar = ' . $db-&gt;qoute($string_value)) ); </code></pre> <p>I failed to prove him wrong, and he failed to prove me wrong. Can you do either?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMSalters
    1. USIvan Krechetov
    plurals
    1. PL
      singulars
      1. LTLinked
    2. 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
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs it OK to allow sometimes dynamic SQL without sanitization?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIs it OK to allow sometimes dynamic SQL without sanitization?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIs it OK to allow sometimes dynamic SQL without sanitization?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COParameterized statements! Parameterized statements! Parameterized statements! http://stackoverflow.com/questions/60174/best-way-to-stop-sql-injection-in-php
      singulars
      1. POIs it OK to allow sometimes dynamic SQL without sanitization?
      1. USCheekysoft
    2. CO@Cheekysoft Sir, have you read the question carefully? We do use parameterized statements. Send your mantra to Zend :)
      singulars
      1. POIs it OK to allow sometimes dynamic SQL without sanitization?
      1. USIvan Krechetov
    3. COWow! Looks like you can bind in delete and update: http://stackoverflow.com/questions/1845153/zend-framework-how-to-delete-a-table-row-where-multiple-things-are-true
      singulars
      1. POIs it OK to allow sometimes dynamic SQL without sanitization?
      1. USIvan Krechetov
 

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