Re: SQL question

I personally think that RPG IO opcodes are much more readable than SQL
statement. Program clarity should triumph number-of-statements it needs
to accomplish the task. In you example SQL statement, if you already
have necessary logic files that allows you to perform it in RPG-Opcodes,
I don't see any reason to use SQL.

There is really nothing bad about the F-spec. For a pure RPG program,
F-spec can quickly tell a programmer what files are being used in the
program and it also gives clue on how those files are used.

One more thing about your SQL statement: If your SQL statement result
in more than one records, the SQL statement will fail. Unless your have
code to check for it, it will fail silently.


Note: My personal experience seems to indicate that RPG opcodes, in most
case, are faster than SQL (I know there are stat that said otherwise).



"David FOXWELL" <David.FOXWELL@xxxxxxxxx> wrote in message
news:<mailman.1259.1231417603.15060.rpg400-l@xxxxxxxxxxxx>...
Hi,

If I understood correctly from a previous thread, the use of SQL in the
example below taken from something I already wrote is not a good idea as
I am doing a single row search.

EXEC SQL

SET : MyField = (

SELECT MYFIELD FROM MYTABLE1 JOIN MYTABLE2 ON ID1 =ID2

WHERE MYOTHERFIELD= : MYSEARCHDATA );

If I were not to use SQL I'd have to code the 2 files in the F specs,
and do 2 CHAINs. I've noticed a lot of people are doing similar quick
fixes.

Sorry to keep asking the same question, but is this example really that
bad?


----------