IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Future consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on Jun 6, 2019

RELATED IDEAS

Support for ON UPDATE CASCADE

Use case: There is a table called release with a primary key id of type integer and an additional column name (the release name). And further tables (e.g. table_x, table_y, …) with a reference (foreign key) to release.id. The working tables are table_x, table_y, a.s.o. and the selects have to be ordered by the foreign key release.id. An ordering by release.name is not possible because of arbitrary release names that are not sortable.

To the discussion that primary keys should not be changed can I say that this use case is not like a change of the release primary key but more like a movement of primary keys/releases and their referenced data to insert a new release and get the desired order.

Needed by Date Jan 1, 2020
  • Guest
    Reply
    |     May 14, 2021

    Of course I can do it this way, but I have many dependent tables with that foreign key on parent_table (release) and have to know them for the update. It's not so easy ;-)

    So it will be still easier and less error prone if the database supports ON UPDATE CASCADE. With your approach I have to do five statements for one dependent table and 4+n for n dependent tables that I have to know. On update cascade does it in one!

    And I have always to know what statements I execute. Because of security and mistakes I can restrict the update on parent_table to priviledged users only.

  • Guest
    Reply
    |     Dec 2, 2020

    You can easily do this this way:

    begin work;

    set constraints foreign_key_constr_name deferred;

    update parent_table set keycol = 15 where keycol = 3;

    update child_table set fkcol = 15 where fkcol = 3;

    commit work;

    This defers checking of the foreign key constraint until the COMMIT WORK is executed at which point everything is fine.

    To my mind ON UPDATE CASCADE is not needed and potentially dangerous.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.