Re: Paging - ADO.NET 2.0
- From: "Landley" <news@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Sep 2005 22:24:12 +0100
I was under the impression that additional information was sent to server
from the provider when such a query is made.
Thus allowing the database engine server-side to move the cursor to whatever
the position is and return the required number of rows.
This would explain our findings with our time tests. Could it be that
different providers do different things. These tests were with an Informix
database using the Informix .NET provider. I have done any further tests
with any other providers.
A confirmation on what the Fill method actually does behind the scenes is
required. Does Microsoft have any documentation regarding this?
Landers.
"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:OhsPhkuvFHA.1716@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> Well, Fill method doesn't alter select command in any way it just ignored
> first set of irrelevant records - thus server side filtering is
> automatically opted out.
> But still those records have to be fetched to client so it can ignore them
> :-).
> If you want do proper paging you'll have to use stored procuderes I think.
>
> --
> Miha Markic [MVP C#]
> RightHand .NET consulting & development www.rthand.com
> Blog: http://cs.rthand.com/blogs/blog_with_righthand/
>
> "Landley" <news@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:erEupTuvFHA.4032@xxxxxxxxxxxxxxxxxxxxxxx
> > Is this true?
> >
> > I was informed that the filtering was done server-side, though my source
> > may
> > have been unreliable.
> >
> > I am using this method in a large image database returning 50 images per
> > page. Our timings getting data back from page 1 and page 1000 were the
> > same.
> >
> > Can you point me at your source of information?
> >
> > Landers
> >
> >
> > "Miha Markic [MVP C#]" <miha at rthand com> wrote in message
> > news:eeJ3RmovFHA.3188@xxxxxxxxxxxxxxxxxxxxxxx
> >> Just note that adapter isn't intelligent enough to skip first records
> >> (before the requested page) and thus it will fetch all records from
zero
> > to
> >> the end of the page.
> >> For example, if you request 3rd page of 10 records it will fetch all 30
> >> records (but will insert only page into the DataTable)
> >>
> >> --
> >> Miha Markic [MVP C#]
> >> RightHand .NET consulting & development www.rthand.com
> >> Blog: http://cs.rthand.com/blogs/blog_with_righthand/
> >>
> >> "Landley" <news@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:e%23ZggUjvFHA.612@xxxxxxxxxxxxxxxxxxxxxxx
> >> >I use the dataadapter.fill method.
> >> >
> >> > One of the overloads allow you to specify a start and a maximum
number
> > of
> >> > rows to return.
> >> >
> >> > To page your results, you'll need to know the number of rows your
query
> >> > will
> >> > return.
> >> >
> >> > Landers.
> >> >
> >> > "Victor H. Passador" <vpassador@xxxxxxxxxxx> wrote in message
> >> > news:%23g2zlHjvFHA.2132@xxxxxxxxxxxxxxxxxxxxxxx
> >> >> Hi !
> >> >>
> >> >> At first, sorry by my bad english ...
> >> >>
> >> >> I need to develop a windows form app. This application must be as
> >> >> agnostic
> >> >> (in database terms) as possible.
> >> >> The application must run against SQL Server 2000, Oracle and/or DB2.
> >> >> I need to implement some kind of paging due to that several queries
> >> >> may
> >> >> returns a great quantity of data.
> >> >> I've heard that SqlExecutePageReader() method doesn't comes with the
> >> > release
> >> >> of ADO.NET 2.0.
> >> >> Is that true ?
> >> >> Would somebody advice me with the best method to achieve this
"paging"
> >> > with
> >> >> ADO.NET 2.0 ?
> >> >>
> >> >> Thanks in advance.
> >> >>
> >> >> Best Regards
> >> >>
> >> >> Victor
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>
.
- References:
- Paging - ADO.NET 2.0
- From: Victor H. Passador
- Re: Paging - ADO.NET 2.0
- From: Miha Markic [MVP C#]
- Re: Paging - ADO.NET 2.0
- From: Miha Markic [MVP C#]
- Paging - ADO.NET 2.0
- Prev by Date: Re: Distinct on a DataSet.
- Next by Date: Re: Generating parameter names in ADO.NET 2.0
- Previous by thread: Re: Paging - ADO.NET 2.0
- Next by thread: Object must implement IConvertible, writing to BLOB
- Index(es):
Relevant Pages
|