Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

preventing access to db

 
Jason Hocker
Ranch Hand
Posts: 132
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I understand if there are multiple clients and one server, the server can maintain one version of the database, and keep it synchronized.
In the standalone architecture, do we need to worry about multiple clients touching the same database at the same time?
 
Nathaniel Stoddard
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No -- in the standalone mode, only one program still has access to the database, the CSR running the program. Always just one program.
 
Theo van Loon
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But how can you make sure that only a single server is running?
 
Jacques Bosch
Ranch Hand
Posts: 319
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You don't need to.
My instructions say:

You may assume that at any moment, at most one program is accessing the database file; therefore your locking system only needs to be concerned with multiple concurrent clients of your server

I'm sure yours says something similar. Take a look.

J
 
Theo van Loon
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jacques i'm delighted to hear this!! I must say perhaps it's wise to keep reading the instructions...
 
Jacques Bosch
Ranch Hand
Posts: 319
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Perhaps yes.
I memorized mine..... (Just joking)
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic