Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't think this is something that would require a plugin. In this case I would write something along the lines of this.</p> <p>This script is assuming the user is making a http POST request to this page, probably by submitting a form somewhere on your website.</p> <p>If any of this looks foreign to you feel free to ask and I'll be happy to clarify :)</p> <pre><code>&lt;?php //Create new database connection $idForPassword = 5; $mysqli = new mysqli("localhost", "DBusername", "DBpassword", "DBName"); //Create new prepared statement $stmt = $mysqli-&gt;prepare("SELECT password FROM sometable WHERE id = ?"); $stmt-&gt;bind_param("i", $idForPassword); // execute query $stmt-&gt;execute(); // bind result variables $stmt-&gt;bind_result($result); $stmt-&gt;fetch(); // Hash the password so we aren't storing a password as plain text in the database // ideally you also add a salt to your password but since this is just an example // I'll leave that part out $password = md5($_POST['password']); if($password == $result) { //allow user access } else { //deny user access } </code></pre> <p>edit: A little more info on <a href="http://php.net/manual/en/faq.passwords.php" rel="nofollow">Salting and Hasing passwords</a>. I'd recommend reading it whenever you get the chance since its a fairly easy way to implement basic level of security if you plan on storing passwords in a database.</p> <blockquote> <p>The security issue with simple hashing (md5 et al) isn't really the speed, so much as the fact that it's idempotent; two different people with the same password will have the same hash, and so if one person's hash is brute-forced, the other one will as well. This facilitates rainbow attacks. Simply slowing the hash down isn't a very useful tactic for improving security. It doesn't matter how slow and cumbersome your hash algorithm is - as soon as someone has a weak password that's in a dictionary, EVERYONE with that weak password is vulnerable.</p> <p>Also, hash algorithms such as md5 are for the purpose of generating a digest and checking if two things are probably the same as each other; they are not intended to be impossible to generate a collision for. Even if an underlying password itself requires a lot of brute forcing to determine, that doesn't mean it will be impossible to find some other bit pattern that generates the same hash in a trivial amount of time.</p> <p>As such: please, please, PLEASE only use salted hashes for password storage. There is no reason to implement your own salted hash mechanism, either, as crypt() already does an excellent job of this.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. PORequiring a Password / Passphrase to view contents of category with Wordpress
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USechochamber
    1. USechochamber
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORequiring a Password / Passphrase to view contents of category with Wordpress
      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. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAfter some fiddling, this worked for me. Thanks for giving me an easy to understand start point. =)
      singulars
      1. PO
      1. USignu5_
    2. CO@ignu5_ glad to hear it! I also went back and elaborated a little about hashing and salting passwords.
      singulars
      1. PO
      1. USechochamber
 

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