SQL statements that exceed 32K in their collective data types currently crash. For example, if you select 10 LVARCHAR columns of 5000 each, totaling 50000 you get an error, crashing the application. This limit is way too low and it is causing our mission critical applications to stop, causing big problems. Even the small Cloudscape database did not have this limitation.
Why is it useful?
|Who would benefit from this IDEA?||All users would benefit from this, allowing to run queries and include practically all fields they need.|
How should it work?
Increase this limit to at least 512K or higher. We do not have a good workaround for this problem other than telling our users not to include all of these fields in their report/document output which is really not a solution and causes serious business problems.
|Priority Justification||Our applications are not able to generate necessary documents, reports, and in some cases this may include medical information and this cannot be left out.|
|Customer Name||M Systems International|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions