Re: dataformatting in nodeJS SQL interface with IBM db2a

Seems like a reasonable RFE.



-----Original Message-----
From: Niels Liisberg [mailto:nli@xxxxxxxxxxxxxxxxx]
Sent: Saturday, March 24, 2018 10:08 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] dataformatting in nodeJS SQL interface with IBM db2a

At better solution would be: set the trim option on the connection since that is already IBM proprietary . Doing it on the select statement would pollute the sql syntax.

Why don't you raise a RFE for both trimming and sql-alike data types in the result-set. I think my friend Jesse Gorzinsky would love that.
lør. 24. mar. 2018 kl. 15.52 skrev Henrik Rützou <hr@xxxxxxxxxxxx>:

Nathan

a lazy programmer (and I'm one) is a programmer that dosn't code 100
similar programs from one end to the other - they have fun making a
program generator that then does the job they do not bother to make
;-)

On Sat, Mar 24, 2018 at 3:10 PM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

Henrik,

The term "lazy programmer" is sometimes used with negative
connotation,

and

other times used with positive connotation. In this case, I don't
fault programmers who would rather not code the full SQL statement,
including
rtrim() function calls required to trim fields.

I was just trying to say that this is a case where invoking a REST
web service API would provide a simpler interface for programmers. A
web-service API would relieve programmers of the verbosity and
ofttimes complexity of coding their own SQL statements.

I'm just suggesting that this is a case where a REST web service API

would

have advantages over Node's db2a interface.



On Sat, Mar 24, 2018 at 7:41 AM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

Nathan

you may call it lazy to want to have a transparent interface that

hasn't

to

be
touched every time you add a new or remove a column to a table.

Especially removing a column will cause errors if you specify

resultsets

by specific field names, imho they sould automatically be removed
from the rest service and that should automatically result in the
field are removed in the UI regardless of code defining the field
may exsist.

We are back to constructing an UI where if you filter the SSN from

UserA

it dosn't appear in his UI but dons't filter it from UserB it
appears - both running on the same code.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://archive.midrange.com/web400.

--
Regards,
Henrik Rützou

http://powerEXT.org <http://powerext.org/>
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list To post a message email: WEB400@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/web400.

--

Best regards

Niels Liisberg
Chief Software Architect
System & Method A/S
Phone +45 70 20 30 10
Mobile + 45 31 15 88 61