Re: [IBMiOSS] Field Length using node.js

"OpenSource" <opensource-bounces@xxxxxxxxxxxx> wrote on 07/14/2016
11:37:41 AM:

From: John Yeung <gallium.arsenide@xxxxxxxxx>
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Date: 07/14/2016 11:38 AM
Subject: Re: [IBMiOSS] Field Length using node.js
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxx>

On Thu, Jul 14, 2016 at 12:01 PM, Kevin Adler <kadler@xxxxxxxxxx> wrote:

Here's what it's reporting for the lengths:

ITITEM=7
ITIDESC=8
ITPRICE=8
ITQTY=6

The Node.js developer confirmed my suspicion that fieldWidth is

returning

the length of the column name (plus a null terminator). It really

returns

the *actual* length of the column name in case of truncation. I

question

why this might be useful to a Node.js developer, since I would have
suspected that the node db adapter would never truncate the column

name.

Interesting. I question why this might be useful to ANY developer,
because, really, who ever needs to know the length of the field NAME?
At least, when would you ever want to know the length of the (full,
untruncated) name, but NOT want the (full, untruncated) name itself?

I questioned it too. It seems they are just passing through the data
returned from the CLI API directly.

fieldPrecise will return the precision (total column width) and

fieldScale

(digits after the decimal) will return the scale.

So for the table in question,
ITITEM should return scale = 15, precision = 0
ITIDESC should return scale = 30, precision = 0
ITPRICE should return scale = 9, precision = 2
ITQTY should return scale = 9, precision = 0

I guess you meant precision = 15, scale = 0 for ITITEM, etc.

John Y.

Yeah, sorry. The way CLI uses the terms precision and scale is totally
backwards to what I think they should be (and how others use the terms as
well). The worst part is I was consciously trying to get it right, since I
figured someone would "correct" me, but alas I mixed them up anyway...