Re: Waiting for a recordset to finish fetching
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Thu, 26 Jul 2007 20:21:09 +0100
Are you sure? I got the impression that JET started to deliver rows before
the rowset population is complete. SQL Server does this too--it delivers
the first rows to ADO.NET (to the provider) when the first buffer is done.
These rows are streamed over in the DataReader as they are made available
on the server. No, JET is not SQL Server and JET's provider is very
different than SqlClient but I would not be surprised if JET started
making rows available before the last one was found--at least to the
DataReader (which is behind the scenes in ADO classic). If the application
tries to update the rows fetched, I have also seen JET open another
connection and start making changes.
Yes I am sure. This is ADO and not ADO.NET.
Server-sided => Open() will return early.
CacheSize records are populated and refilled once MoveNext() empties the
buffer.
Very database and provider-specific
Client-sided, synchronous => Open() will only return when the entire rowset
is in client-sided memory.
That is true for all providers.
Client-sided, asynchronous => Open() will return early and you can monitor
the progress watching Status as the rest of the records are fetched.
I am not sure how ADO.NET differs.
Maybe sometime I will play with DataReader's
Cheers
Stephen Howe
.
- References:
- Re: Waiting for a recordset to finish fetching
- From: Stephen Howe
- Re: Waiting for a recordset to finish fetching
- From: JoelB
- Re: Waiting for a recordset to finish fetching
- From: Stephen Howe
- Re: Waiting for a recordset to finish fetching
- From: William Vaughn
- Re: Waiting for a recordset to finish fetching
- Prev by Date: Re: Waiting for a recordset to finish fetching
- Next by Date: Re: How to protect data within MS access?
- Previous by thread: Re: Waiting for a recordset to finish fetching
- Next by thread: Re: Waiting for a recordset to finish fetching
- Index(es):
Relevant Pages
|
|