Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1
  • Across two different question pages on this I have checked, your solution seems to be the shortest, most logical, and easiest to implement. I can't comment on performance on hundreds-of-gigabytes-of-data, but it sure does the trick where I needed it. People who complain that this approach is too verbose need to embrace the 'Structured' aspect of SQL ;p Commented Feb 4, 2015 at 21:53