Yes, that is what we considered. But it really still ran into the same
issue where if you're on page 5, new records are inserted and you start
going back, the pages "aren't the same" as they were going TO page 5.
To me, it's not an issue and actually a good thing. But, I guess in this
case the customer isn't sure that's what they want.
Bradley V. Stone
BVSTools, Inc.
[1]www.BVSTools.com
[2]www.eRPGSDK.com
Jim Franz wrote:
I did something with a similar issue (new records inserted), and stored the
"top" of the current screen, on Prev: read back xx records (whatever a
screen is) loading an array, then write detail from the array (it's in
reverse order).
If Next: take last record of screen +1 and load going forward.
Either back or forward, new records will appear.
Have to allow the Prev may find less than full screen if getting back to 1st
page - take 1st record & start over.
Lots of reading but it works.
jim franz
----- Original Message -----
From: "Bradley V. Stone" [3]<bvstone@xxxxxxxxxxxx>
To: [4]<WEB400@xxxxxxxxxxxx>
Sent: Thursday, July 30, 2009 11:30 AM
Subject: [WEB400] SQL Cursor Positioning with Web Application
For years I've written Web Applications using dynamic SQL to build
result
sets.
For example, if a user wants to search a transaction history, I give
them
a bunch of fields that they can use to select records, and also options
to
sort by any of the columns. Pretty simple when using dynamic SQL.
For paging I store the RRN of the result set so when they click
"previous"
or "next" I use relative positioning with my SQL. Works great.
Now in this particular case where we're querying a transaction file it
gets updated very often. Lets say a few records every minute. So lets
say they view page one, click next so they're on page 2. Then next so
they're on page 3. During this time, 10 new records were added. So
they
go back which should be page 2, but it's really (for lack of a better
term) page 2.5 since more records have been added. :) So it loses the
positioning.
So, without using persistance, temp files, etc.. anyone have any ideas
here? Or is this a case where "that's just how it will work".
Thanks!
--
Bradley V. Stone
BVSTools, Inc.
[1]www.BVSTools.com
[2]www.eRPGSDK.com
References
Visible links
1. [5]
http://www.bvstools.com/
2. [6]
http://www.erpgsdk.com/
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: [7]WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [8]
http://lists.midrange.com/mailman/listinfo/web400
or email: [9]WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [10]
http://archive.midrange.com/web400.
References
Visible links
1.
http://www.bvstools.com/
2.
http://www.erpgsdk.com/
3. mailto:bvstone@xxxxxxxxxxxx
4. mailto:WEB400@xxxxxxxxxxxx
5.
http://www.bvstools.com/
6.
http://www.erpgsdk.com/
7. mailto:WEB400@xxxxxxxxxxxx
8.
http://lists.midrange.com/mailman/listinfo/web400
9. mailto:WEB400-request@xxxxxxxxxxxx
10.
http://archive.midrange.com/web400
midrange.com
