Many of us have lived in this space a looong time - don't assume that we
haven't heard your request, we are just digging deeper because we don't like
your current implementation (i.e. temp file) which many of us believe could
potentially be eliminated.

Cursor read or regular I/O doesn't make a difference.

Could make all the difference.


For some reason, I thought that in V5R4, or another version, you were
given the ability to do a SELECT ... FOR XML

I have heard of this feature in some of the WebSphere/Rational SQL tooling,
but have not used it. I don't believe it is part of i5OS but instead a set
of Java .jar files that offer the functionality.

Aaron Bartell
http://mowyourlawn.com

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Michael_Schutte@xxxxxxxxxxxx
Sent: Wednesday, October 31, 2007 7:26 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Faster HTML Output.

It helps with getting it off the server faster and puts the burden on the
client's computer. Has I have said and some of you guys keep forgetting...
the problem is not getting the data with the SQL statement. The problem is
reading the large amount of data. So to use the suggestion of "not" using
the temp table doesn't help. Cursor read or regular I/O doesn't make a
difference.

For some reason, I thought that in V5R4, or another version, you were given
the ability to do a SELECT ... FOR XML (or something similar to that). But
I haven't found any documentation on it.


Michael Schutte
Admin Professional
Bob Evans Farms, Inc.
"The Secret's the Sauce! Enjoy our new Bob-B-Q Pulled Pork Knife & Fork
Sandwich!"




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.