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 updateson 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
Add generated always for each row on update as row change SESSION_USER
Currently exists in Db2 to change current timestamp on INSERT and UPDATE with generated statement like:
create table myschema.mytable (id int, last_timestamp timestamp not null generated always for each row on update as row change timestamp)
insert into myschema.mytable (id) values (1) update myschema.mytable set id = 2 where id =1
I would like to have something similar for SESSION_USER, to automatically add current session user on INSERT and UPDATE like (this is actual idea):
create table myschema.mytable (id int, last_user varchar(128) not null generated always for each row on update as row change SESSION_USER)
Currently work-around is: create table myschema.mytable (id int, last_user varchar(128) with default session_user) above solves the SESSION_USER for INSERT statement, but for UPDATE we are required to write after update trigger. Now we are required to manually add after update triggers for few hundred tables.
Do not place IBM confidential, company confidential, or personal information into any field.