Databases
StackOverflow2013
Postsdbo
POUnderstanding this query further
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnderstanding this query further
    primarykey
    data
    text
    <p>All,</p> <p>Via much research, I have managed to get the following query to work, however I don't fully understand what it's doing. I now need to adapt it a little, hence need to understand it more thoroughly.</p> <p>The query looks in several tables to provide a list of results with one row per group of results as opposed to having one row per result (which would have too much duplication of information)</p> <p>The query is:-</p> <pre><code>SELECT od_date, tbl_order.od_id, tbl_order_item.od_item_id, pd_code, item_code, pd_name, &gt;cust, pd_type, tbl_order_item.od_item_id, tbl_order_item.test_suite_name, MAX( IF( tbl_lab_item.test_name = 'Test 1', tbl_lab_item.test_result, NULL ) ) AS TEST1, MAX( IF( tbl_lab_item.test_name = 'Test 2', tbl_lab_item.test_result, NULL ) ) AS TEST2, MAX( IF( tbl_lab_item.test_name = 'Test 3', tbl_lab_item.test_result, NULL ) ) AS TEST3, MAX( IF( tbl_lab_item.test_name = 'Test 4', tbl_lab_item.test_result, NULL ) ) AS TEST4, MAX( IF( tbl_lab_item.test_name = 'Test 5', tbl_lab_item.test_result, NULL ) ) AS TEST5, MAX( IF( tbl_lab_item.test_name = 'Test 6', tbl_lab_item.test_result, NULL ) ) AS TEST6 FROM tbl_item INNER JOIN tbl_item ON tbl_lab_item.od_item_id = tbl_item.od_item_id INNER JOIN tbl_order ON tbl_order.od_id = tbl_item.od_id WHERE tbl_order.od_date LIKE '%$orderDate%' AND customer_id = '%custID%' GROUP BY tbl_lab_item.od_item_id </code></pre> <p>This give me the following output:-</p> <pre><code>Order Date | Order ID | Item Id | &lt;snip - other columns&gt; | TEST1 | TEST2 | TEST 3 ...etc 09/09/2013 | 2 | 1 | | 10 | 20 | 30 ...etc </code></pre> <p>What I want to do now is display any result which is less than 50 as '&lt; 50' rather than have the actual number displayed. Ditto for '>100'.</p> <p>I'm not sure how to add this logic into the above query, or even whether it is possible.</p> <p>Any help you can offer would be greatly appreciated.</p> <p>Many thanks, Jason</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJason
    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. POUnderstanding this query further
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you want all tests (TEST1 TEST2 etc..) to be checked for being less than 50? Should all of them be less than 50, or just one is enough?
      singulars
      1. POUnderstanding this query further
      1. USKelu Thatsall
    2. COThat's a good question. At the moment, all of them, however I suspect that the next step may be to have different levels for each test, so TEST1 may be <50 but TEST2 would be <60. My experience is that retaining the flexibility is usually the best way to go.
      singulars
      1. POUnderstanding this query further
      1. USJason
 

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