Hi James,
First, you're best off posting this to
microsoft.public.dotnet.framework.adonet. There are very knowledgeable
people there who can answer this question definitively.
I am not as strong as you are on interfaces but I am very strong on ado .net
in general and the for each loop. Yes, the data comes out in the order in
which it was filled, but I don't understand the underpinings as you do, so
with particular regard to the ienumerator interface, I can't help you.
HTH,
Bernie Yaeger
"James Jensen" <ja**************@hotmail.com> wrote in message
news:fb**************************@posting.google.c om...
I ran into a snippet of code that uses a FOR EACH loop to step through
the rows in a Dataset.Table object. I understand that the FOR EACH
statement implements the MoveNext function of the IEnumerator
interface of the InternalDataCollectionBase object.
I was wondering if anyone knew whether or not the iterator in this
case uses a certain hashing algorithm? The table object in question
is filled via a stored procedure that returns its data unordered.
Could it be that the data comes out from the iterator in the same
order that it was filled?