+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 11 to 14 of 14

Thread: oledbdatareader vs dataset?

  1. #11
    picoflop is offline VB.NET Forum Genius picoflop a notorious wonder 'round these woods picoflop a notorious wonder 'round these woods picoflop a notorious wonder 'round these woods picoflop a notorious wonder 'round these woods
    .NET Framework
    .NET 3.5 (VS 2008)
    Join Date
    Feb 2009
    Age
    41
    Posts
    158
    Reputation
    97

    Default

    Quote Originally Posted by cjard View Post
    Yeah because the world really fell over didn't it?
    Personally I never believed that the world would implode on 1.1.2k

    Still it remains a fact, that fixing old programs (like making sure that a grandgrandma doesnt become a toddler) was a quite expensive tasks. Didn't they even teach ppl Cobol again, bc many old apps where done with it and the original programmers wherent available anymore?

    Anyway: Depending on the situation it DOES make sense to look into the future. Though "performance" probably is not the biggest problem, because if the problem arises somewhere in the future, available hardware will probably be able to handle it.

  2. #12
    cjard's Avatar
    cjard is offline VB.NET Forum All-Mighty cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute
    .NET Framework
    .NET 2.0 (VS 2005)
    Join Date
    Apr 2006
    Age
    66
    Posts
    6,676
    Reputation
    927

    Default

    Quote Originally Posted by picoflop View Post
    Personally I never believed that the world would implode on 1.1.2k

    Still it remains a fact, that fixing old programs (like making sure that a grandgrandma doesnt become a toddler) was a quite expensive tasks. Didn't they even teach ppl Cobol again, bc many old apps where done with it and the original programmers wherent available anymore?
    Yep, and the doom mongers said "too little, to late"

    The y2k problem was known about and being catered for in the 80s in the systems where it mattered, so there was some future thinking going on.

    I also got to thinking more about my statement "cross bridges when you come to them" and the parallel of the millennium bug and I dont really see it. Concluding that a lack of the former precludes events such as the latter is like responding to me that I'm advocating developing a program that ius broken and doesnt work because you'll cross that [doesnt work] bridge when you come to [release the program] -> there's a base level of foresight that's necessary and also it must be considerd what is actually worth thinking about in terms of future need.

    Depending on the situation it DOES make sense to look into the future. Though "performance" probably is not the biggest problem, because if the problem arises somewhere in the future, available hardware will probably be able to handle it.
    Totally agree, though Moore's law shouldnt be an excuse for burning up resources unnecessarily but the games industry tends to do it (release games that are possibly beyond the capabilities of all but the very best hardware) and it drives the hardware companies to play a useful game of catchup. Quite mercenary, IMHO

  3. #13
    picoflop is offline VB.NET Forum Genius picoflop a notorious wonder 'round these woods picoflop a notorious wonder 'round these woods picoflop a notorious wonder 'round these woods picoflop a notorious wonder 'round these woods
    .NET Framework
    .NET 3.5 (VS 2008)
    Join Date
    Feb 2009
    Age
    41
    Posts
    158
    Reputation
    97

    Default

    the parallel of the millennium bug and I dont really see it
    Because I tend to disagree that y2k was a "known problem". Hardly none (I guess only of course) of the original programmers ever expected that their code would be used more or less unchanged for more than a decade.

    Back to topic:
    I would think that "dataset vs datareader" is a major design decision, that can not easily be changed somewhere in the future without more or less completely rewriting most parts of the app?

  4. #14
    cjard's Avatar
    cjard is offline VB.NET Forum All-Mighty cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute cjard has a reputation beyond repute
    .NET Framework
    .NET 2.0 (VS 2005)
    Join Date
    Apr 2006
    Age
    66
    Posts
    6,676
    Reputation
    927

    Default

    Quote Originally Posted by picoflop View Post
    I would think that "dataset vs datareader" is a major design decision, that can not easily be changed somewhere in the future without more or less completely rewriting most parts of the app?
    It's probably something you'd migrate gradually..

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

     

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts