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



I *always* appreciate your insight, Buck, but you nailed it: "everyone has
their own situation they have to deal with" No need for me to get started
on a rant.. Lol.

- Dan

On Tue, Oct 23, 2018 at 12:16 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 10/23/2018 11:45 AM, Dan wrote:
Thanks Buck! That is where I was headed if I couldn't do this in native
SQL.

I'm not going to preach; everyone has their own situation they have to
deal with. I should have been forthcoming with my reasoning though. I
have done very similar things; written a routine in RPG, deployed it
into who knows how many programs [1], and then wanted similar
functionality in SQL, so I wrote it in SQL, and deployed that into who
knows how many places.

And then there was a legitimate need to change the way that routine
works. Imagine, in your example, that you also want to translate high
EBCDIC values to upper as part of this text cleanup.

With two separate code blocks, deployed in many hard-to-find places,
that simple change is now a lot of work. If I'd encapsulated the single
RPG sub-procedure into an SQL UDF then all consumers of that business
function would have been handled simply.

That's a lot of words to explain how I always seem to regret multiple
implementations of the same business function.

[1] The lack of built-in cross reference tooling is probably my only
genuine gripe with the platform.


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.