Databases
StackOverflow2013
Postsdbo
POMySQL query - joining two tables producing duplicate results
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMySQL query - joining two tables producing duplicate results
    primarykey
    data
    text
    <p>I'm running the following MySQL query in PHP.</p> <pre><code>"SELECT * FROM `challenges`,`verifications` WHERE (`challenges`.`user_id`='".$this-&gt;record['id']."' OR `challenges`.`opponent_id`='".$this-&gt;record['id']."') AND `challenges`.`is_verified`='0' AND (`challenges`.`status`='in-progress' OR `challenges`.`status`='pending') AND ( (`verifications`.`user_id`='".$this-&gt;record['id']."' OR `verifications`.`opponent_id`='".$this-&gt;record['id']."') AND (`verifications`.`user_verified`!=NULL AND `verifications`.`opponent_verified`=NULL) ) LIMIT 100"; </code></pre> <p>This query is returning duplicate records for some reason. If anyone has any insights, I would greatly appreciate it.</p> <p>Here is the structure for the two tables (challenges and verifications):</p> <p>Challenges Table:</p> <pre><code>CREATE TABLE `challenges` ( `id` int(11) NOT NULL auto_increment, `wager` int(11) NOT NULL, `type` varchar(255) NOT NULL, `user_id` int(11) NOT NULL, `opponent_id` int(11) NOT NULL, `start_date` date NOT NULL, `date_created` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, `start_time` time NOT NULL, `is_verified` tinyint(1) NOT NULL default '0', `status` varchar(255) NOT NULL default 'pending', `winner_id` int(11) default NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=0 ; </code></pre> <p>Verifications Table:</p> <pre><code>CREATE TABLE `verify` ( `id` int(11) NOT NULL auto_increment, `user_id` int(11) NOT NULL, `opponent_id` int(11) NOT NULL, `challenge_id` int(11) NOT NULL, `user_verified` int(11) default NULL, `opponent_verified` int(11) default NULL, PRIMARY KEY (`id`), UNIQUE KEY `challenge_id` (`challenge_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=0; </code></pre> <p>Thanks for your help, and if you need any more info please let me know.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTaryn
    1. USjjfrizzle
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMySQL query - joining two tables producing duplicate results
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMySQL query - joining two tables producing duplicate results
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMySQL query - joining two tables producing duplicate results
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou should avoid using `SELECT *` (use a column list) and using implicit joins as they are both poor practice.
      singulars
      1. POMySQL query - joining two tables producing duplicate results
      1. USKermit
    2. CO@njk why do you consider `select *` a bad practice?
      singulars
      1. POMySQL query - joining two tables producing duplicate results
      1. USJohn Dvorak
    3. COThe query deserves a proper formatting.
      singulars
      1. POMySQL query - joining two tables producing duplicate results
      1. USJohn Dvorak
 

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