Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The right way to do this is to test for null first:</p> <pre><code>function ccdeleteuser($emailaddress) { $ConstantContact = new ConstantContact("basic", "apikey", "usr", "pwd"); $SearchContact = $ConstantContact-&gt;searchContactsByEmail($emailaddress); // first makes sure that the 0 index of of SearchContact is accessible at all // then it ensures that only something "truthy" will trigger delete -- this // means that if $SearchContact[0] is null, the function won't try to delete if( $SearchContact &amp;&amp; isset( $SearchContact[0] ) &amp;&amp; $SearchContact[0]) $DeleteContact = $ConstantContact-&gt;deleteContact($SearchContact[0]); else echo "Can't do nothin'"; // do something useful? } </code></pre> <p>With try... catch, you might make it look like this:</p> <pre><code>function ccdeleteuser($emailaddress) { $ConstantContact = new ConstantContact("basic", "apikey", "usr", "pwd"); $SearchContact = $ConstantContact-&gt;searchContactsByEmail($emailaddress); try { // keep this... it is still useful if( $SearchContact &amp;&amp; isset( $SearchContact[0] ) &amp;&amp; $SearchContact[0]) $DeleteContact = $ConstantContact-&gt;deleteContact($SearchContact[0]); else echo "Can't do nothin'"; } catch( Exception $e ) { // I'm making up a function "log" which will record that an error // has taken place. It is a good idea to always log all exceptions // so that you don't accidentally obfuscate something important log( $e-&gt;getMessage() ); // do something useful } } </code></pre> <p>As a general note, it is always best to act proactively to prevent exceptions and not simply catch them after the fact. I'll even go so far as to say that you should consider it a rule to always do everything in your power to prevent the possibility of an exception and only use try... catch as a last possible resort.</p>
    singulars
    1. This table or related slice is empty.
    1. POPHP Error Message Help and Try/Catch
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScwallenpoole
    1. UScwallenpoole
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPHP Error Message Help and Try/Catch
      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. VTAcceptedByOriginator
    1. COThanks for your answer, the first one worked perfectly! It's one of those situations where you get so tunnel visioned on doing "try and catch" that you forget there is a simpler (and more effective) way!
      singulars
      1. PO
      1. USChris Cummings
 

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