AW: SQL Multiple Prepared Statements - Best Practice

Hi Michael,

first using DDS described logical files in an SQL statement is almost the
worst thing you can do!
1. The query optimizer only takes the field selections, join conditions and
select/omit clauses from DDS described logical files an rewrites the SQL
statement based on the underlying physical files. Th

Mit freundlichen Gru?en / Best regards

Birgitta

"Shoot for the moon, even if you miss, you'll land among the stars."
(Les Brown)

-----Ursprungliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]Im Auftrag von Michael Ryan
Gesendet: Samstag, 5. August 2006 22:48
An: RPG programming on the AS400 / iSeries
Betreff: SQL Multiple Prepared Statements - Best Practice


I have a program that's currently using 7 different logicals over the same
physical. No select/omit criteria - just different keys. Depending on user
selection (via function keys), a subfile is populated using a different
logical. Because of some (new) additional selection criteria, I've decided
to rewrite using embedded SQL.

Here's my question: Should I be using 7 different Prepares and Executes and
Opens of cursors? Is there a different way of doing it? I know I can't use
Execute Immediate because I'm using a Fetch. Looking for best practices or
suggestions.

Thanks...
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.