Re: iNav SQL scripts see last row

On 1/27/11 6:36 AM, Loyd Goodbar wrote:

You're depending on the assumption that DSPPFM or RUNQRY *NONE PFILE
places the newest records at the end/bottom of the file, and that
reuse deleted records is off. SQL tools, SQL methods. :)

On Thu, Jan 27, 2011 at 7:43 AM, David FOXWELL wrote:

I've got into the habit of keeping an iNav sql scripts window
open, since I started saving my scripts and organising them. In
this case, I just ran a program on the i that inserted a new record
in a large file. To quickly examine that record, then, I have to
use the good ol' greenscreen. Nice, the way it reacts as soon as
you hit a button :-)

FWiW: Although "RUNQRY *NONE PFile" is implemented via the CQE versus the SQE, each Query Engine implementation is a query interface to the database, such that the order of returned rows can not be expected to be retrieved nor presented in arrival order; not in any order, other than a requested order\collation. Thus even assuming the B=Bottom on the displayed report for a default [PF only] query to see the last row as the most recently added, may be incorrect. Neither the Query/400 nor its run-time via RUNQRY enable a collation feature which provides for the arrival sequence access path as a means for data retrieval, and the default query just presents the results as obtained by the database from the CQE query request, which may be in any undetermined order reflected only by the optimizer chosen path(s) to the data. So while a default query may seem to /always/ return data in arrival order, that effect can not legitimately be expected\assumed; the only valid assumption is that the correct set of rows are returned, irrespective of any order.

Regards, Chuck