× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Wed, 2016-08-10 at 10:38 -0500, Darryl Freinkel wrote:
Something I have not had to deal with before.

I have to create a table that has about 400 fields which are mostly VARCHAR
and of length 100 to 2000 each. So I get SQL0101.

SQL0101 is "statement to long or complex"

At a wild guess (I'm not a sql bod, just going from a google), the issue
is not the size of the fields but is the total length of the sql
statement. By reducing the field size you have shortened the statement
length.

I guess a workaround would be to create the table with X fields, then
alter (I think) the table to add the outstanding fields.


I have always heard that the table sizes can go into the yoda byte sizes
but never a record length maximum.

For now I have reduced the field sizes to 50 chars to get passed the issue.

This is a V5R4 system.

Is there a work around or different way to use these huge record sizes?

TIA
--
Darryl Freinkel



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.