× 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.


  1.  Home
  2. MIDRANGE-L
  3. May 2019

Re: SQL insert error - value for column too long

On Tue, May 28, 2019 at 2:05 PM Robert Rogerson <rogersonra@xxxxxxxxx> wrote:

As Rob and Joe pointed out the columns must be in the same positions.
To get this to work with in INSERT statement you would have to list all the
columns.
INSERT INTO wlklib/dshpf34 COLUMNS(col1, col2, ...)
( select a.* from DSHXFR/DSHPF34 a )
make the order of the columns in dshpf34 match the column order of
dshxfr/dshpf34.

More specifically, Steve needs to keep in mind that SELECT simply
returns a list of values for each row. Those values have no names
associated with them. So the columns specified in the COLUMNS portion
of the INSERT statement have to appear in the same order that they are
defined in DSHXFR/DSHPF34.

Alternatively you could use a CPYF with FmtOpt(*MAP *DRP) and this should
popule correctly

This is much simpler, though not as flexible (SQL lets you easily
filter or sort, for example).

John Y.

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.