Re: [IBMiOSS] Trouble with numeric columns in pyodbc -- OPENSOURCE

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

Subject: Re: [IBMiOSS] Trouble with numeric columns in pyodbc
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 1 Aug 2019 11:36:52 -0600
List-archive: <https://archive.midrange.com/opensource/>
List-help: <mailto:opensource-request@lists.midrange.com?subject=help>
List-id: IBMi Open Source Roundtable <opensource.lists.midrange.com>
List-post: <mailto:opensource@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/opensource>, <mailto:opensource-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/opensource>, <mailto:opensource-request@lists.midrange.com?subject=unsubscribe>

On Thu, Aug 1, 2019 at 11:26 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

Error('01004', '[01004] [IBM][System i Access ODBC Driver]String data
right truncation. (30016) (SQLExecDirectW)')

If it's valid on Windows, I can't see why it fails on IBMi.

Ooh, I saw that in Azure migrating some data from IBM i to Azure managed
SQL.

Turned out to be a decimal data type declared wrong.

As an Amazon Associate we earn from qualifying purchases.

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.