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 Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Dec 15, 2017

"EXTEND TABLE" SQL statement

To day there are no elegant way to map OO class extensions direct in Db2. So it would be appreciated that Db2 invent a new statement that Extend a table as a new table with extra columns. In effect - Db2 makes a internal maintained one-to-one relation between the original table and the "extension" - Or think about is a section of new columns added to the existing table BUT hidden form the original table I/O "record layout"


Use Case:

Lets say you have a "person" and some persons can be "employees". The we can created the table(s) like this


create table person (
id int generated always as identity unique ,
name varchar(256)
);

extend table person as employee (
salary dec(9,2)
)

if you now do:

Select * from person;

you will have the:
id , name

if you do a:

Select * from employee;

Then because the "employee" now extends the "person" you will have:
id, name, salary

Expected behaviour in any OO environment.


Idea priority Medium
  • Guest
    Reply
    |
    Dec 8, 2020

    IBM does not intend to provide a solution to this request at this time, so it is being closed.

    It would be possible to implement something similar to this by using additional tables and views.

  • Guest
    Reply
    |
    Dec 18, 2017

    The CEAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed.

    Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC 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 CEAC, see http://www.comeur.org/i4a/pages/index.cfm?pageid=3285

    Dawn May - CEAC Program Manager