Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I used to be a friend of centralizing sanitation as much as possible, but extensive discussion on SO (<a href="https://stackoverflow.com/questions/1809843/why-is-filter-input-incomplete"><strong>for example here</strong></a>) has changed my mind. Definitely worth a read.</p> <p>I submit to you the following practice:</p> <p>In a central validation routine, do no sanitation, or just "rough" checks (say, for data type) and size ("$_POST["category_name"] should not be larger than 200 bytes.") </p> <p>Mark incoming variables as <strong>unsafe</strong> (e.g. <code>$unsafe_id = $_POST["category_name"];</code>). Store them in whatever controller / class / construct you have available for it.</p> <p>Sanitize data <strong>where it is used</strong>. If incoming data is used in a <code>exec</code> call for example, do the necessary sanitation directly in front of the call:</p> <pre><code> $safe_category_name = escapeshellargs($unsafe_category_name); exec("external_binary -category_name '$safe_category_name'"); </code></pre> <p>if the same data is then used in a, say, mySQL query, again sanitize it in front of the call:</p> <pre><code> $safe_category_name = mysql_real_escape_string ($unsafe_category_name); mysql_query("SELECT * FROM items WHERE category_name = '$safe_category_name'"); </code></pre> <p>(this is just an example. If starting a project from scratch, you will want to use PDO and prepared statements, which takes away the hassle of escaping incoming data in this context.)</p> <p>if the same data is then output in a web page, again do the sanitation directly in front of the call:</p> <pre><code>$safe_category_name = htmlspecialchars($unsafe_category_name); echo "&lt;span&gt;$safe_category_name&lt;/span&gt;"; </code></pre> <p>This practice </p> <ul> <li><p>Establishes a workflow that assumes there are unsafe variables that need to be dealt with first, which leads to a safer programming style IMO. </p></li> <li><p>Prevents unnecessary conversions.</p></li> <li><p>Helps fight the illusion that there is a one-click method to make input "safe." There isn't. Sanitation depends 100% on context.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POWhere to sanitize PHP $_POST[] input?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPekka 웃
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhere to sanitize PHP $_POST[] input?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COEven easier, if it's an ID in vanilla PHP you can just use $id = (int) $_POST['id'] to make it safe.
      singulars
      1. PO
      1. USPhil Sturgeon
    2. CO@Phil the `$id` was meant to be an example of arbitrary string data. I changed the variable, as id is usually numeric, you're right. Cheers.
      singulars
      1. PO
      1. USPekka 웃
 

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