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. General Programming
  3. C#
  4. How to get rid of interval checkings

How to get rid of interval checkings

Scheduled Pinned Locked Moved C#
databasetutoriallounge
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.
  • L Offline
    L Offline
    leone
    wrote on last edited by
    #1

    Hi friends. I have a database and people send some info into this db. But sending time is totally random. So now i check this db every 20 seconds and refresh my program according to new data. But as my user count increases, i need a more efficient approach. I mean how can my program know that somebody added something new into db.

    L 1 Reply Last reply
    0
    • L leone

      Hi friends. I have a database and people send some info into this db. But sending time is totally random. So now i check this db every 20 seconds and refresh my program according to new data. But as my user count increases, i need a more efficient approach. I mean how can my program know that somebody added something new into db.

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Informing each client of each change in the database is a known anti-pattern; not only does it generate quite some traffic, it also moves the problem of concurrent edits to the UI.

      leone wrote:

      i need a more efficient approach

      Add a table that holds the "last" datetime that you "modified" your tables. Would consist of two columns; datetime and the name of the table that's changed. Have the client query that table to see if there are any changes. Means fetching data from a table, and the last modification-datetime for that table :)

      Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

      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