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.
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
See this idea on ideas.ibm.com
I'm trying to check if a serial value has reached its upper limit. I noticed the following unpleasant behaviour.
In the sysmaster tables sysptnhdr and sysactptnhdr the currently used serial values are in three fields for the datatypes serial, serial8 and bigserial.
If my serial approaches the upper limit for integer data types, the easiest way is to change it to a serial8 or bigserial.
During the alter table, the current value from serial is now copied into the column of the new type. Unfortunately the value of serial is not reset to 0 or NULL.
This means that a value check still reports a dangerously high serial value, even though the table no longer has this data type.
Since you can have both types serial and serial8/BigSerial in a table in parallel, you must now also check the syscolumns of the affected database to suppress this message.
At least for databases with non-english locale this is even more difficult, because you cannot access directly from sysadmin or sysmaster.
My suggestion is that only the field of the data type that is used is filled with the current serial value and the others are reset to 0 or NULL.
A repro for this behaviour can be found in the support case TS002868693.
Needed by Date | Sep 30, 2020 |
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.
A work around to this problem at ALTER time when changing the type of a column from, for example, SERIAL to BIGSERIAL would be to first set the next serial number to zero then alter the type to BIGSERIAL setting the next value manually as part of the alter:
ALTER TABLE mytab MODIFY keycol SERIAL(0);
ALTER TABLE mytab MODIFY keycol BIGSERIAL(16,010,001);
I agree that this behavior should be automatic, especially given that a table can contain more than one serialized type as long as they are different types (ie one SERIAL, one BIGSERIAL, and one SERIAL8)!