Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><code>SQL Server</code> lacks native bitwise aggregates, that's why we need to emulate them.</p> <p>The main idea here is to generate a set of bits from <code>0</code> to <code>15</code>, for each bit apply the bitmask to the value and select <code>MAX</code> (which will give us an <code>OR</code> for a given bit), then select the <code>SUM</code> (which will merge the bit masks).</p> <p>The we just update the first <code>lngInternetPK</code> for any given <code>(lngContactFK, strValue)</code> with the new value of <code>lngValue</code>, and delete all duplicates.</p> <pre><code>;WITH bits AS ( SELECT 0 AS b UNION ALL SELECT b + 1 FROM bits WHERE b &lt; 15 ), v AS ( SELECT i.*, ( SELECT SUM(value) FROM ( SELECT MAX(lngValue &amp; POWER(2, b)) AS value FROM tblmInternet ii CROSS JOIN bits WHERE ii.lngContactFK = i.lngContactFK AND ii.strAddress = i.strAddress GROUP BY b ) q ) AS lngNewValue FROM ( SELECT ii.*, ROW_NUMBER() OVER (PARTITION BY lngContactFK, strAddress ORDER BY lngInternetPK) AS rn FROM tblmInternet ii ) i WHERE rn = 1 ) UPDATE v SET lngValue = lngNewValue; ;WITH v AS ( SELECT ii.*, ROW_NUMBER() OVER (PARTITION BY lngContactFK, strAddress ORDER BY lngInternetPK) AS rn FROM tblmInternet ii ) DELETE v WHERE rn &gt; 1 </code></pre> <p>See this article in my blog for more detailed explanations:</p> <ul> <li><a href="http://explainextended.com/2009/07/13/sql-server-aggregate-bitwise-or/" rel="nofollow noreferrer"><strong>SQL Server: aggregate bitwise OR</strong></a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POUpdate column to be different aggregate values
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USQuassnoi
    1. USQuassnoi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUpdate column to be different aggregate values
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThis is good. The only problem is that each contact can have multiple distinct emails. So we don't want to delete all other emails associated with an contact.
      singulars
      1. PO
      1. USCorey Sunwold
    2. CO@csunwold: so you want to keep one instance of each `(contact, email)` pair?
      singulars
      1. PO
      1. USQuassnoi
    3. CO@Quassnoi: correct. There should be one instance of an email for every contact, but multiple distinct emails are allowed for each contact.
      singulars
      1. PO
      1. USCorey Sunwold
 

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