Re: SQL Result Paging

I thought about this and made changes so that shouldn't happen (shouldn't
cause when using LINQ "magic happens"). The time wasn't affected.

--
Mike Wills
http://mikewills.me


On Mon, Mar 11, 2013 at 3:05 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

The question is the connection. Do you open and close connection to the
AS/400 with every call? If you maintain the connection between calls, then
you have state because it is running in a single job on the iSeries until
the connection is closed.

The other way to do this in a stored procedure is to use the fetch multiple
rows. That is extremely fast. On the first page you only fetch the first
less say 25 records and return them. On the next page you fetch 50 records
and return only the last 25. Each page you fetch more but because you are
using fetch multiple rows you would probably never even notice it and they
would already be cached.


On Mon, Mar 11, 2013 at 1:59 PM, Mike Wills <mike@xxxxxxxxxxxx> wrote:

We don't maintain state and I am not sure how I could in .NET if
our architecture would allow it.

--
Mike Wills
http://mikewills.me


On Mon, Mar 11, 2013 at 2:57 PM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

A stored procedure maintains state ...

That works IF the client maintains a persistent connection. I once

worked

with a group Java developers who vowed that they would never use

persistent

connections. Later they caved in and implemented "stateful" connections

to

QZDASOINIT jobs in order to implement paging and offer better

performance.

Frankly, I think IBM i handles stateful connections well, so this

sounds

like a good solution.

-Nathan

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.