|
On 5/12/2016 4:45 PM, Jose Perez wrote:
I Agree with Paul, 6000 Characters for a query? that will make yoursql
program very complicated, what I would do if I were you I would work my
in modules or pieces better said and for every piece I would produce the
result in global temporary table and work from my global temporary table,
it is not a good practice to have a so big sql in just one line.
I very much agree that a giant SQL statement is a sign that something
could be improved.
But.
I have also written automated tooling to generate a dynamic SQL
statement based on user input (no injection!) and some of those
program-created statements are... big.
--
--buck
Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!
--
This is the RPG programming on the IBM i (AS/400 and 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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
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.