• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

database multi user vs single user

 
james airey
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In an effort to get started, I am tempted to write the database as a single user system, with no locking, and once I have that working correctly, I will start worrying about multiple users, record locking and thread safety, etc.
Would anyone advise against that approach?
 
George Marinkovich
Ranch Hand
Posts: 619
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That was my approach. It allows one to make progress from the beginning. It's a reasonable place to start, and the multiuser locking and synchronization scheme can be added later once one figures out how to do it.
Likewise, I developed the client GUI for the standalone operating mode first. The networking scheme can be added later once one figures out how to do it. I think you will find that the GUI code you develop for the standalone mode will work as well for the network operating mode (except for making the database connection).
Hope you enjoy the project,
George
 
Dave Knipp
Ranch Hand
Posts: 146
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would agree that this approach is appropriate especially since locking can become very detailed and difficult as you begin to test it. If you implement all the basics first i think you will be a much better position if you tried to do it all at once.
Good luck!
Dave
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic