On Wed, 2016-08-10 at 17:01 +0100, Wilson, Jonathan wrote:
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
I guess a workaround would be to create the table with X fields, then
alter (I think) the table to add the outstanding fields.
My mistake, further investigation shows "complex" can mean row length
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?
This mailing list archive is Copyright 1997-2019 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