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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Support additional single-byte encodings for column-organized tables
The latest updates to DB2 have added the support of codepage 809 (ISO8859-1) for databases using column-organized tables. . This is good for many Western customers, who are able to avoid switching to Unicode (and paying the penalty of 2x or 3x character string sizes). . This is still not so good for other (mostly, Cyrillic) customers, who can use either UTF-8 with CHAR/VARCHAR (3x string sizes) or UTF-16 with GRAPHIC/VARGRAPHIC (2x string sizes). . 2x or 3x character data size mostly kills all the benefits of BLU compression, on many databases. . It would really help if codepages 915 (ISO8859-5) and 1251 (windows-1251) were also supported by column-organized tables - in fact, that would be enough not just for Russia, but also for many other countries using Cyrillic characters.
Do not place IBM confidential, company confidential, or personal information into any field.