Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. ADO.NET disconnected model doubts

ADO.NET disconnected model doubts

Scheduled Pinned Locked Moved Database
csharpdatabasevisual-studioquestionworkspace
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    Gilles Plante
    wrote on last edited by
    #1

    Hi all, I see (almost) everywhere that the disconnected model for database access is fabulous. Granted, this is the easiest way in VS 2005 to build an application. And for shure, there are fine things in there, but I have doubt about a few things: - in a multi-user environment, user A starts the application, and while he browses records, user B changes some of them. Unless user A specifically refreshes the data, he does not see the updated data - records are not updated as soon as a user moves to another record. Say a user have been adding records for the last 5 minutes and have not hit the SAVE button. Then a loss of power occurs: say goodbye to the changes - how about transactions Is it that there are things that I don't understand, or am I right in fearing this model ? Thanks

    Gilles Plante

    S 1 Reply Last reply
    0
    • G Gilles Plante

      Hi all, I see (almost) everywhere that the disconnected model for database access is fabulous. Granted, this is the easiest way in VS 2005 to build an application. And for shure, there are fine things in there, but I have doubt about a few things: - in a multi-user environment, user A starts the application, and while he browses records, user B changes some of them. Unless user A specifically refreshes the data, he does not see the updated data - records are not updated as soon as a user moves to another record. Say a user have been adding records for the last 5 minutes and have not hit the SAVE button. Then a loss of power occurs: say goodbye to the changes - how about transactions Is it that there are things that I don't understand, or am I right in fearing this model ? Thanks

      Gilles Plante

      S Offline
      S Offline
      S Douglas
      wrote on last edited by
      #2

      Gilles Plante wrote:

      am I right in fearing this model

      No these are all things that you need to account for while devoloping. Make use of time stamp columns often. Ultimatly the disconnected model is less stress on the SQL server. This topic has come up several times on the message board, search it for "disconnected database" and you will find long conversations about how to deal with some of the issues you brought up.


      I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups