There is no valid reason that I'm aware of.
In fact, I think that latter statement should run slightly faster.
I'm guessing what happened is probably that access plan built by the query
optimizer differs for the two statements and it's saved somewhere (program,
package, plan cache), so you're best off forcing a one-time access plan
rebuild for the latter statement (there is a QAQQINI option to effect this).
Other than that, I'd suggest contacting IBM and reporting this little oddity
as a defect.
HTH, Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i5/OS and OS/400
www.centerfieldtechnology.com
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.