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.

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

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

I have tried SELECT RTRIM(*) FROM XXX and seached the net but can't find
a
simple solution.


I agree that it would be better for trailing blanks to be removed at the
server, before transmission to the client. If you're using SQL, you could
explicitly name the columns and invoke rtrim(column_name). Lazy programmers
may not like that because of the verbosity added to the statement.

This question dovetails with the discussion that I started about using a
REST web services interface as opposed to the Db2 and iToolkit interface to
interact with IBM i. A generic server side procedure could be written that
automates the trimming of trailing blanks. Just make that part of the
interface, so that application developers don't need to address it
themselves.
--
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.





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.