Bill Roper (billroper) wrote,
Bill Roper
billroper

Hopelessly Bad

Some time ago, the folks in charge of our web interface decided that we should return data as a .NET DataSet. This may not have been the happiest choice.

Apparently, the indexing in the .NET DataSets is badly broken. I'm trying to do a Select on two columns to retrieve -- in the desired order! -- the 7400 points that are defined as rows in a particular DataSet. The columns are both primary sort keys.

This takes 25 seconds or so to run. If I comment out the Select statement, it takes less than a second to complete the loop.

Supposedly you can do the query against the contained DataRowCollection instead of against the DataTable and that will be faster. It isn't.

Supposedly you can force the table to create an index for a column and it will be faster. That might be true, but doesn't work when you need to search on more than one column.

Overall, this is so broken it isn't even funny.

I think I'll go to England.
Tags: filk, musings, work
Subscribe

  • The X-Refactor

    I actually don't so much mind refactoring code, as long as I am doing something that will improve the code base. For instance, today I worked with…

  • Sofa, So Good

    They were having one of their periodic sales at La-Z-Boy this weekend. Given the condition of the sleeper sofa in the living room and the couch in…

  • This and That

    Gretchen and I had fun doing our concert for Festival of the Living Rooms today. And it was nice to knock some of the rust off, because there's not…

  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 1 comment