ILDASM seems to be the most important tool to get information on how things work. One of our apprentice has used this tool even several times.
But one question is remaining: why do the DataTable update the index at that time and not when the DataRow is added into the table? our application is an windows service and more important than the speed is the memory usage. The result is that i'm not allowed to create a DataRow when it is not garanteed that this row become later a member of the table! tobias > By running ILDASM on System.Data.dll. > > This is pure speculation, but I think a DataTable *must* keep > a record of > every row it creates since it was last reset. If it didn't, > it would have > to re-align its indexes every time you created or deleted a > DataRow. That's > a pretty expensive operation, and the trade-off between > memory and speed was > made in favour of speed. > > If you cloned the table, the new copy's indexes will be > clear, then you can > dispose of the original. Should save you some memory. Or > maybe you need a > different approach altogether? > > Jim > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
