Databases
StackOverflow2013
Postsdbo
POAll rows with at least # qualifying rows, per day
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAll rows with at least # qualifying rows, per day
    primarykey
    data
    text
    <p>Say we have a table like this:</p> <pre><code>**tablename** ID Name Size Date AtStore1 AtStore2 1 Apple Medium 20120101 Yes 2 Pear Medium 20111231 Yes Yes 3 Lemon Small 20111231 Yes Yes 4 Orange Small 20111231 Yes 5 Carrot Medium 20111231 Yes 6 Potato Small 20111231 Yes 7 Celery Large 20111231 Yes 8 Onion Medium 20111231 9 Tomato Medium 20111231 10 Apple Medium 20111231 12 Pear Medium 20111230 Yes Yes 13 Lemon Small 20111230 Yes 14 Orange Small 20111230 Yes 15 Carrot Medium 20111230 Yes 16 Potato Small 20111230 17 Celery Large 20111229 18 Onion Medium 20111229 Yes 19 Tomato Medium 20111229 </code></pre> <p>Can we construct an efficient query that retrieves ALL data per row where:</p> <ul> <li>"Yes" AtStore1 rows where there are at least 4 "Yes"es in AtStore1 on that day single day<br> OR (inclusive)</li> <li>There is a "Yes" in AtStore2</li> </ul> <p>Also acceptable is if only the first parameter is satisfied, i.e. the forward lookup of rows. I can probably script the AtStore2 part with PHP if necessary. All of my attempts have failed miserably; my attempts on how to write the question effectively in Google weren't fruitful either.</p> <p>(Answers breaking things out into different parts of code in PHP are fine too, I just want something reasonably efficient.)</p> <p>For this example table, these would be the expected rows:</p> <pre><code>ID Name Size Date AtStore1 AtStore2 1 Apple Medium 20120101 Yes 2 Pear Medium 20111231 Yes Yes 3 Lemon Small 20111231 Yes Yes 4 Orange Small 20111231 Yes 5 Carrot Medium 20111231 Yes 6 Potato Small 20111231 Yes 7 Celery Large 20111231 Yes 12 Pear Medium 20111230 Yes Yes 14 Orange Small 20111230 Yes 15 Carrot Medium 20111230 Yes 18 Onion Medium 20111229 Yes </code></pre> <p>As you can see</p> <ul> <li>Jan 1 2012<br> -No Yeses in AtStore1<br> -AtStore2 has a Yes so the row is returned</li> <li>Dec 31<br> -5 Yeses in AtStore1, so those are returned (AtStore2 Yeses in ID 2 and 3 would have sufficed as well)<br> -Also has ID 7 since there is a Yes in AtStore2</li></li> <li>The rest of the rows returned were only because of Yeses in AtStore2</li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USLiandri
    1. USLiandri
    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. POAll rows with at least # qualifying rows, per day
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAll rows with at least # qualifying rows, per day
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo, what you want is. For any single day, if there are 4 Yes in AtStore1, show all rows for that day. If not, show only rows with Yes at AtStore2 for that day. Correct?
      singulars
      1. POAll rows with at least # qualifying rows, per day
      1. USypercubeᵀᴹ
    2. CONo, show only the Yes rows. However, AtStore1 needs at least 4 in a day in this example to qualify (a Yes in AtStore2 would basically override it). Maybe separating the queries or a UNION will be necessary?
      singulars
      1. POAll rows with at least # qualifying rows, per day
      1. USLiandri
    3. COIt's still not clear. What rows should be the returned in your example?
      singulars
      1. POAll rows with at least # qualifying rows, per day
      1. USypercubeᵀᴹ
 

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