• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • Row Value Expressions Simplify Complex Row Selection

    February 10, 2015 Ted Holt

    If you like mile-long, messy, obfuscated, hard-to-read SQL, the kind that makes sane people want to cuss and spit on everybody and everything, then this tip is not for you. And please don’t apply for a job in my shop. But if you have better things to do than debug SQL, then I have a simple but clever technique for you.

    Suppose the chief bean counter walks into your office and asks for a spreadsheet of general ledger transactions. He wants the current-month transactions for accounts 120, 135, 180, 192, and 198. Here’s how a novice would write the query (except that he might not format it quite so prettily):

    select * from glxacts
     where date between '2015-02-01' and '2015-02-28'
       and (account=120 or account=135 or account=180 or
            account=192 or account=198)
    

    And he would get thousands of transactions, which the following few represent:

    SEQ   DEPARTMENT  ACCOUNT  DATE           AMOUNT
      1       22         120   2015-02-01      75.76
      2       22         180   2015-02-01      25.02
      3       34         135   2015-02-01      44.33
      4       34         180   2015-02-01      15.69
      5       34         192   2015-02-01       5.20
      6       46         120   2015-02-01      28.22
      7       46         198   2015-02-01      16.27
      8        1         120   2015-02-01      88.99
     10       22         135   2015-02-01      88.99
     11       34         120   2015-02-01      88.99
     12       46         135   2015-02-01      88.99
    

    But you are not a novice, and for that reason you know that you can simplify the query this way:

    select * from glxacts
     where date between '2015-02-01' and '2015-02-28'
       and account in (120, 135, 180, 192, 198)
    

    The IN operator really cleaned up the code!

    The bean counter needs a refinement of the query. He zeroes in on certain accounts for certain departments. (I’ll keep it to three for simplicity. Assume he wants to know about a lot more.)

    • For department 22, account 180.
    • For department 34, account 135.
    • For department 35, account 198.

    You could do this:

    select * from glxacts
     where date between '2015-02-01' and '2015-02-28'
       and (   department = 22 and account = 180
            or department = 34 and account = 135
            or department = 46 and account = 198  )
    

    That would give you the correct results.

    SEQ   DEPARTMENT  ACCOUNT  DATE           AMOUNT
    ===   ==========  =======  ==========     ======
      2       22         180   2015-02-01      25.02
      3       34         135   2015-02-01      44.33
      7       46         198   2015-02-01      16.27
    

    But doesn’t it seem a shame to have replaced that handy IN operator with a bunch of ugly AND’s and OR’s? I have good news! You can still use IN when comparing two or more fields!

    select * from glxacts
     where date between '2015-02-01' and '2015-02-28'
       and (department, account) in
            (values(22,180), (34,135), (46,198))
    

    Think of the VALUES keyword as a mechanism to create a table on the fly.

    Is that fine, or what!?

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Tags:

    Sponsored by
    Midrange Dynamics North America

    Git up to speed with MDChange!

    Git can be lightning-fast when dealing with just a few hundred items in a repository. But when dealing with tens of thousands of items, transaction wait times can take minutes.

    MDChange offers an elegant solution that enables you to work efficiently any size Git repository while making your Git experience seamless and highly responsive.

    Learn more.

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Sponsored Links

    Northeast User Groups Conference:  25th Annual Conference, March 30 - April 1, Framingham, MA
    Profound Logic Software:  Reach Your Modernization Goals. Register for the February 25 Webinar now!
    System i Developer:  Upgrade your skills at the RPG & DB2 Summit in Dallas, March 17-19

    IBM Layoffs Not As Dramatic As Rumored Orchestrating Your API-Enabled Assets On IBM i

    Leave a Reply Cancel reply

Volume 15, Number 03 -- February 10, 2015
THIS ISSUE SPONSORED BY:

ProData Computer Services
COMMON
WorksRight Software

Table of Contents

  • Create Excel Spreadsheets From DB2 Data With PHPExcel
  • Row Value Expressions Simplify Complex Row Selection
  • Git To It

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • Public Preview For Watson Code Assistant for i Available Soon
  • COMMON Youth Movement Continues at POWERUp 2025
  • IBM Preserves Memory Investments Across Power10 And Power11
  • Eradani Uses AI For New EDI And API Service
  • Picking Apart IBM’s $150 Billion In US Manufacturing And R&D
  • FAX/400 And CICS For i Are Dead. What Will IBM Kill Next?
  • Fresche Overhauls X-Analysis With Web UI, AI Smarts
  • Is It Time To Add The Rust Programming Language To IBM i?
  • Is IBM Going To Raise Prices On Power10 Expert Care?
  • IBM i PTF Guide, Volume 27, Number 20

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2025 IT Jungle