Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This should work.</p> <pre><code>DECLARE @ids TABLE(n int); INSERT INTO @ids (n) VALUES (1000); INSERT INTO @ids (n) VALUES (2000); INSERT INTO @ids (n) VALUES (3000); SELECT il.* INTO #InvoiceLineQuery FROM [InvoiceLine] il INNER JOIN @ids i ON il.invoiceId = i.n SELECT letter.text id, CASE WHEN pos.maxPos = pos.minPos THEN pos.maxPos ELSE NULL END AS position, letter.text, CASE WHEN price.maxPrice = price.minPrice THEN price.maxPrice ELSE NULL END AS price, 0 AS isRecordDeleted, CASE WHEN moveUP.text IS NOT NULL THEN 'yes' ELSE 'no' END AS moveUP, CASE WHEN moveDOWN.text IS NOT NULL THEN 'yes' ELSE 'no' END AS moveDown FROM (SELECT il.text FROM #InvoiceLineQuery il GROUP BY il.text HAVING count(il.position) = (SELECT count(1) FROM @ids)) letter INNER JOIN (SELECT il.text, MAX(il.position) maxPos, MIN(il.position) minPos FROM #InvoiceLineQuery il GROUP BY il.text) pos on letter.text = pos.text INNER JOIN (SELECT il.text, MAX(il.price) maxPrice, MIN(il.price) minPrice FROM #InvoiceLineQuery il GROUP BY il.text) price on letter.text = price.text LEFT JOIN (SELECT upNeighbour.text FROM (SELECT mainLine.text text, upLine.text upText FROM #InvoiceLineQuery mainLine INNER JOIN #InvoiceLineQuery upLine ON mainLine.position = upLine.Position + 1 AND mainLine.invoiceId = upLine.invoiceId) upNeighbour GROUP BY upNeighbour.text,upNeighbour.upText HAVING count(upNeighbour.upText) = (SELECT count(1) FROM @ids)) moveUP ON letter.text = moveUP.text LEFT JOIN (SELECT downNeighbour.text FROM (SELECT mainLine.text text, downLine.text downText FROM #InvoiceLineQuery mainLine INNER JOIN #InvoiceLineQuery downLine ON mainLine.position + 1 = downLine.Position AND mainLine.invoiceId = downLine.invoiceId) downNeighbour GROUP BY downNeighbour.text,downNeighbour.downText HAVING count(downNeighbour.downText) = (SELECT count(1) FROM @ids)) moveDOWN ON letter.text = moveDOWN.text DROP TABLE #InvoiceLineQuery </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POFind which pairs of records' positions can safely be switched in a combined set of records
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRealUlysse
    1. USRealUlysse
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthanks for the answer, but it doesn't yield correct results. With the given data, line C should have moveDown = no but your query makes it a yes. I haven't explored your query yet so maybe is it only partially wrong...
      singulars
      1. PO
      1. USDaniel
    2. COActually with the other set of data (see my last edit of the day), the results are not correct at all. So, nop, this is not it yet. Thanks for your time though....
      singulars
      1. PO
      1. USDaniel
    3. COIf I understand you, lines can only move up when their up neighbour are the same in all invoice. And it work the same way with down neighbour?
      singulars
      1. PO
      1. USRealUlysse
 

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