Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It looks telcoId is primary unique in telco table, but can be multiple in other tables (which makes sense), unfortunately if you try to join single (1) to multiple1 (2) to multiple2 (2) to multiple3 (3), it'd create 1 * 2 * 2 * 3 = 12 rows, which explains the messy multiple2 and multiple3.</p> <p>So instead of doing that single DB call, you'll be looking at less efficiency by running separate queries, getting the telco info first, then making individual DB calls for each telco on telcoCall, telcoData, telcoSMS.</p> <p>Or if you just want the speed and don't care about clean code, you can just use what you have right now, but stack up the if conditions:</p> <p>EDIT 1: Edited to fix logic flaw, for some reason Gaussian elimination comes to mind</p> <pre><code>// Stacking order determined by your SQL ORDER BY: t.telcoName, c.callName, d.dataName, s.smsName if($telcoId == $row['telcoId']) continue; //telco stuff... if($callId == $row['callId']) continue; //call stuff... if($dataId == $row['dataId']) continue; //data stuff... if($smsId == $row['smsId']) continue; //sms stuff... </code></pre> <p>EDIT 2: Another slower way that requires less brainwork</p> <pre><code>if($telcoId != $row['telcoId']) { //telco stuff... callArrayTemp = array(); dataArrayTemp = array(); smsArrayTemp = array(); } if(!in_array($row['callId'], callArrayTemp[])) { callArrayTemp[] = $row['callId']; //call stuff... } if(!in_array($row['dataId'], dataArrayTemp[])) { dataArrayTemp[] = $row['dataId']; //data stuff... } if(!in_array($row['smsId'], smsArrayTemp[])) { smsArrayTemp[] = $row['smsId']; //sms stuff... } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POJSON data encoded are repeated
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USScott Yang
    1. USScott Yang
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJSON data encoded are repeated
      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
    1. COI tried your suggestion, but there is only one data each.
      singulars
      1. PO
      1. USJahm
    2. COYou are right, logic failure there, I'll repair it by introducing an array.
      singulars
      1. PO
      1. USScott Yang
 

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