Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Apr 19, 2018

Generate/consume JSON boolean in DB2 JSON_ functions

It would be useful to have the ability to generate/consume the JSON boolean type in the JSON_TABLE and JSON_OBJECT functions.
Since SQL does not have a boolean data type, there is no direct casting to the JSON boolean.
I suggest providing two "sub" functions, that could be used in the JSON_TABLE and JSON_OBJECT functions, to perform the casting.


Use Case:

I suggest something along the following lines...

Two “functions” for use within JSON_TABLE and JSON_OBJECT - along the lines of…

JSON_TABLE(:json, ‘lax $'
COLUMNS( JSON_FROM_BOOLEAN(“ISLAZY", ‘Y', 'N') CHAR(1) PATH ‘$.islazy' ))

or

JSON_TABLE(:json, ‘lax $'
COLUMNS( “ISLAZY” JSON_FROM_BOOLEAN(‘Y', 'N') CHAR(1) PATH ‘$.islazy' ))

and

JSON_OBJECT( ‘lazy' JSON_TO_BOOLEAN(:ISLAZY, ‘Y', 'N') )

Parameters being column, true value, false value/ If the value is neither true or false, then null

This gives the choice of providing any values for true/false (‘1'/‘0', ‘Y'/'N', ‘J'/'N', ‘YES'/‘NO' etc.)


Idea priority High
  • Guest
    Reply
    |
    May 3, 2022
    IBM believes that the request described has been solved and is available with IBM i 7.5.

    The Boolean data type has been added to SQL. JSON Boolean values of true and false (with no delimiters) can be generated by the JSON scalar functions such as JSON_OBJECT, and can be interpreted by JSON_TABLE as a Boolean data type.

    For a description of the Boolean enhancement, see https://www.ibm.com/support/pages/node/6575531
  • Guest
    Reply
    |
    Feb 26, 2021

    IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it.

  • Guest
    Reply
    |
    Mar 21, 2019

    The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to address.

    The CEAC recognises that to introduce Boolean in the Db2 for i is a major undertaking, however, it is strategically important. Therefore as a 1st step would be to offer users "sub" functions for casting which would be quicker and simpler to implement.

    Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

    Therese Eaton – CEAC Program Manager, IBM

  • Guest
    Reply
    |
    Sep 18, 2018

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. Although there are other solutions, this one would simplify the process.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |
    Sep 18, 2018

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. Although there are other ways to do this, this solution would simplify the process.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |
    Apr 20, 2018

    Isn't that just a CASE statement? Albeit a cool SQL UDF in general, I couldn't want it to be JSON-only.