Re: Where to post ideas for RPG

-----CRPence <crpbottle@xxxxxxxxx> wrote: -----

On 19-Aug-2016 13:25 -0700, Mark Murphy wrote:

This is craziness. There is no way I am going to jump into the SQL
precompiler,

Seems a common\recurring theme here on this list; apparently,
somehow, a pre-compiler so complicates coding, that _avoidance_ is the
typical policy.? I do not understand the logic, nor any rationale
stated in the past messages [IIRC, mostly just _any excuse_ used as
rationalization for avoidance; e.g. "I once had this problem back on
v3r# when..." or "I do not want any SQLRPGLE modules in my Service
Program that currently has only RPGLE" modules], and I expect the quite
legitimate issue for lack of SQL pre-compiler would be so rare as to
seem non-existent.

In addition to the points Barbara raised, even a simple SET initiates a call to SQLROUTE. That is a lot of overhead there just to choose which value to assign to a field.

And,
This ten line program:

dcl-s field1 Packed(7:0);
dcl-s value1 Int(10);
dcl-s value2 Float(8);

exec sql set option sqlca = *no;

exec sql
set :field1 = max(:value1, :value2);

return;

is expanded to 54 lines! If I omit sqlca = *no, that increases to 75 lines.

How often, when a new RPG user comes to this list and asks a trivial question, do we see things like "Let me Google that for you", or "Read the Friendly Manual". I know that the database just doesn't really care that it is being disturbed to answer a trivial question that the asker should have been able to answer for itself, and with less effort than was required to even ask the question in the first place. The fact that we can do a thing, doesn't mean we should.

Of course, all I really wanted was to notify folks of a new RFE. Though, I suppose that a debate on it's merits is warranted.

Mark Murphy