RE: Simple report pgm using embedded SQL

Well you know what they say about opinions.

But the fact of the matter is there's only two places you have to have cursors...

Reports and Subfiles.

And as I said in my other message, thus the word "probably" in my motto.

Personally, I feel the motto works great for RPG programmers moving to SQL as it help them to remember
to think Set-based instead of record at a time.

How many times have you seen an SQLRPG program with a single record fetch, followed by some if
statements followed by and UPDATE WHERE CURRENT?

Charles

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Monday, November 05, 2007 3:03 PM
To: Midrange Systems Technical Discussion
Subject: RE: Simple report pgm using embedded SQL

As this is the specific reason that cursors are supported in
HLL languages, I hardly see a design issue with using a
cursor to generate a report.

I think Charles would be hard pressed to find a reasonable
alternative to cursors, if given that the result set is of
varying row counts (as is often the case with report
printing). Perhaps that statement was made in a thread with
specific requirements (and when taken in context, could be
supported), but as a general purpose constraint, I think its
a bit too much...

jmo,
Eric

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.