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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
NOT NULL limitation violation of VARCHAR2 in case federated SELECT ''(empty charactor) from Oracle compati Db2 to Native Db2
[Situation] There is a federated system between VARCHAR2 compatibility off w/ NOT NULL limitation column defined table (actual source table) and VARCHAR2 compatibility on w/ NOT NULL limitation column defined nick name (federated) table. [Current design] When some application submit a query which contains the varchar2 column to the nickname table, if the result set from the source table contains ""(empty charractor), it become the NOT NULL limitation violation to go back to error code to the application.
[ideal design] VARCHAR2 column is populally used in Oracle DB. Originally VARCHAR2 compatibility function comes from Oracle compatibility enhancement activity, so if we strongly request current Oracle user to replace their current Oracle system, above situation will be frequently encountered.
[Request action] So, it should be modified not to get not null violation when federated select query from VARCHAR2 compatibility ON column table (incl. '' empty charactor) to VARCHAR2 compatibility OFF column table.
Do not place IBM confidential, company confidential, or personal information into any field.