|
I got an interesting message in the joblog for a new RPGSQL I'm testing. This is the SQL that was run: Update DMVDRMST Set AMDUE = 0 AMDUE is defined as 7P 2 The joblog has SQL7939 which says: Message . . . . : Data conversion required on INSERT or UPDATE. Cause . . . . . : The INSERT or UPDATE values can not be directly moved to the columns because the data type or length of a value is different than one of the columns. The INSERT or UPDATE statement ran correctly. Performance, however, would be improved if no data conversion was required. The reason data conversion is required is 2. <snip> -- Reason 2 is that the INSERT or UPDATE value is a numeric type that is different than the type of column AMDUE. <more snip> For grins and giggles, I changed the SQL to Update DMVDRMST Set AMDUE = 00000.00 and got the same message, which is really what I expected would happen. I realize that I'm getting the correct results and it's simply an efficiency issue, but hey, inquiring minds want to know. What's it looking for? Thanks.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.