Databases
StackOverflow2013
Postsdbo
POSQL not recognizing equal values
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL not recognizing equal values
    primarykey
    data
    text
    <p><strong>UPDATE:</strong> I figured out a large part of what caused my problem. When I queried the database to find the data type, it correctly returned CHAR(4) for t2.sale_code.</p> <p>However, the GUI did not display leading zero's. t3.sale_code did not have leading zeros in the file that populated the table. That's what caused my confusion and I corrected the zero problem. Now it joins without any CAST or other manipulation.</p> <p><em><strong></em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>__<em>_</em>____</strong>_I have a query:</p> <pre><code>SELECT t1.id, t2.sale_code, t3.sale_code, t3.title FROM t1 INNER JOIN t2 ON t1.id = t2.id INNER JOIN t3 ON t3.id = t2.id </code></pre> <p>There are some different one-to-many relationships that I can't control that induce duplication. I need to do this:</p> <pre><code>WHERE t2.sale_code = t3.sale_code </code></pre> <p>However, this just won't work. I'm not sure what I'm doing wrong. I can manually make it work:</p> <pre><code>SELECT t1.id, t2.sale_code, t3.sale_code, t3.title FROM t1 INNER JOIN t2 ON t1.id = t2.id AND t2.dt &gt; t1.dt_active AND t2.dt &lt; t1.dt_inactive INNER JOIN t3 ON t3.id = t2.id WHERE t2.sale_code = 4 AND t3.sale_code = 4 </code></pre> <p>For example, this returns a proper matched pair of <code>sale_code</code>'s. However, when I compare them directly (`WHERE t2.sale_code = t3.sale_code) it returns no results. Am I doing something wrong here?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJeffrey Kramer
    1. USJeffrey Kramer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSQL not recognizing equal values
      1. USAna
      1. VTFavorite
    1. COWhat is the data type of sale_code in each table?
      singulars
      1. POSQL not recognizing equal values
      1. USStingyJack
    2. CODoes `sale_code` have the same datatype in both tables?
      singulars
      1. POSQL not recognizing equal values
      1. USHart CO
    3. COThat was my first thought too, they both *should* be VARCHAR(4). I'm going to check one more time just to make sure though. If they are different types will they still respond to the `>` logic the same way and just not join?
      singulars
      1. POSQL not recognizing equal values
      1. USJeffrey Kramer
 

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