Databases
StackOverflow2013
Postsdbo
POPHP true & 'true' difference
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP true & 'true' difference
    primarykey
    data
    text
    <p>Quick question. Is there a difference between</p> <pre><code>$success = true; </code></pre> <p>and</p> <pre><code>$success = 'true'; </code></pre> <p>I know they are not '<code>==</code>' to each other, but is there a difference in using them? </p> <p>EDIT: I found that using '===' instead of '==' when seeing if $success is false solved my problem. My question now is that, should I just use strings in a case like below, and stick with '=='?</p> <pre><code> $User-&gt;ProcessLogin(); $loginsuccess = $User-&gt;ProcessLogin(); if ($loginsuccess == true) { echo "&lt;big&gt;Success&lt;big&gt;&lt;br /&gt;"; echo "&lt;p&gt;We are now redirecting you to the member area.&lt;/p&gt;"; echo "&lt;meta http-equiv='refresh' content='=2;MyAccountNEW.php' /&gt;"; } elseif ($loginsuccess == false) { echo "&lt;span class='sorry'&gt;&lt;b&gt;Sorry, your account could not be found.&lt;/span&gt;&lt;/b&gt;&lt;div id='shopperlogin'&gt; &lt;img class='shopperlogintext' src='images/shopperlogin.png'&gt; &lt;br /&gt; &lt;form method='post' action='loginNEW.php' name='loginform' id='loginform'&gt; &lt;fieldset&gt; &lt;label for='username'&gt;Username:&lt;/label&gt;&lt;input type='text' name='username' id='username' /&gt;&lt;br /&gt; &lt;label for='password'&gt;Password:&lt;/label&gt;&lt;input type='password' name='password' id='password' /&gt;&lt;br /&gt; &lt;input type='submit' name='login' id='login' value='Login' /&gt; &lt;/fieldset&gt; &lt;/form&gt;&lt;/div&gt;"; } </code></pre> <p>Here's part of the class..</p> <pre><code> function ProcessLogin() { if (!empty($_POST['username']) &amp;&amp; !empty($_POST['password'])) { $username = mysql_real_escape_string($_POST['username']); $password = md5(mysql_real_escape_string($_POST['password'])); $checklogin = mysql_query("SELECT * FROM users WHERE Username = '".$username."' AND Password = '".$password."'"); if(mysql_num_rows($checklogin) == 1) { $row = mysql_fetch_array($checklogin); $email = $row['EmailAddress']; $_SESSION['Username'] = $username; $_SESSION['EmailAddress'] = $email; $_SESSION['LoggedIn'] = 1; $this-&gt;loggedin = true; $success = true; } else { $success = false; } return $success; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USasdfasdfasdfasdf
    1. USasdfasdfasdfasdf
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    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. POPHP true & 'true' difference
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPHP true & 'true' difference
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPHP true & 'true' difference
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou can keep it a lot simpler since you're only interested in whether or not the loginstatus is set, and it doesn't matter what it's set to. The var $loginsuccess will always be empty by default, unless something (whatever) is returned. So in the ProcessLogin() function, simply "return true;" instead of using the $success variable. Then test for: if ($loginsuccess) { // great, it worked } else { // fail }. It's also best to use the original form, instead of outputting the same form on fail with duplicate code. Then when need to change something, you only have to fix the original/single form.
      singulars
      1. POPHP true & 'true' difference
      1. USAlec
 

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