Hi,
Dynamic SQL is only needed if you have to maintain your tables/views
dynamically or if you want to write something completely flexible, i.e. a
dynamic list generator that works for any file where you can select any
column or in an web application when the SQL statement is built on the fly.
... almost everything else can be done with static SQL.
Dynamic SQL has to execute several steps at runtime, that are not necessary
for static SQL, for example sysntax checking,
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Michael Ryan
Gesendet: Friday, 14.6 2013 14:20
An: Midrange Systems Technical Discussion
Betreff: Dynamic vs. Static SQL
Anyone have a good explanation or link regarding when dynamic or static
should be or must be used? I always make stuff work, but I don't know if I
fully understand the distinction. Friday fodder. :)
Thanks!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
