IBM Data and AI Ideas Portal for Customers

Hide about this portal

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,

Post an idea
Upvote ideas that matter most to you
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.

I BM 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

create a foreign key allowing one to one tables relationships

See this idea on ideas.ibm.com

Our Primary Key and Foreign key constraints always have allowed creaing and ensuring '1 to many' table relationships. After researching, there is no direct way to implement such a case with Informix. The only safe way is to create a primary key on the 'parent' table, a unique index on the 'child' table plus a trigger with references that will catch insert and delete. This trigger will fire a SPL that will count the rows in the parent table matching the new key. If 1 row, the child row is created, else the SP returns an error. Same principle for DELETE

Needed by Date

Mar 31, 2020

Post comment

Guest

Reply
| Dec 2, 2020

All you have to do is to create a PRIMARY KEY or UNIQUE constraint on the child table's foreign key column that points back to the parent table. Then the child table can only have a single row that references each parent table row. No need to formalize this in syntax!

0 reply Hide replies

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.