Geert-Jan
Fri Jul 21 07:35:45 CDT 2006
Hello Miha,
It is not the looping that is the cause, as it's the same amount of
actions performed.
We use mainly DataTable.Select to find rows, no updates.
And, as mentioned before, it is not slower on all computers, but on
some DataTable methods are much slower when AllowDBNull=true
//get all successors
sfilter = String.Format(usCulture, "Loknummer='" +
tiRow["Locnumber"] + "' AND " + locGanttDepartureString
+ " >= #{0:g}# ", tiRow[locGanttArrivalString]);
rows = table.Select(sfilter, locGanttDepartureString);
Geert-Jan Gorter
proLOGiT Office & Logistics Software Development
Dortmund / Gemany
Miha Markic [MVP C#] schrieb:
> Can you show us some code that shows your loop?
>
> --
> Miha Markic [MVP C#, INETA Country Leader for Slovenia]
> RightHand .NET consulting & development www.rthand.com
> Blog:
http://cs.rthand.com/blogs/blog_with_righthand/
>
> "Geert-Jan" <gortergj@cityweb.de> wrote in message
> news:1153305339.320704.84030@m73g2000cwd.googlegroups.com...
> > Hi,
> >
> > We have a C# programm running on .NET 1.1
> > I have found that on some PC's the performance decreases when using
> > AllowDBNull=false on a DataColumn. By looping extensively through many
> > DataRows in the DataTables, this becomes evident: the application is
> > twice as fast without those codelines.
> > Strangely, on other systems I detect no differences.
> > Has anyone else seen this behaviour, or, even better, an explanation?
> >
> > Thanks
> >
> > Geert-Jan
> >