×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
first of all: use whatever is the easiest way for your needs. You won’t notice measurable differences in 99.9 % of all cases. Most important for static sql is, that the compiler could do a complete verification of your sql statement, including type checking for all parts of the statement.
some remarks to other postings:
- injection is not an very important point to DB2. Harmfull attacks are mostly based on sending 2 statements as one and this doesn’t work for DB2/400.
- working setbased is fine for read only (fetching 1000 rows in a blockfetch is nearly as fast as fetching one row), for update processing transaction is more important than speed (use commitment control!!!)
- performance benefits for static sql are mostly overestimated. Preparing once, executing multiple times is as fast as static, dynamic sorting with a case construct is not faster than dynamic prepare of a statement.
D*B
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: RPG SQL: Prepared Statement v. Cursor, (continued)
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.
midrange.com
