Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    "Another concern I have is 2 people getting a lock for the same item, however I believe that is a race condition I am comfortable with" - using a database transaction around the acquisition of the lock should prevent such race conditions. Commented Jan 9, 2018 at 7:36
  • Most database engines (of the relational sort, at least) have built in support for this. It's a very common concept in the RDBMS world, and even "toy" databases handle it well enough, given that you tell it you want optimistic or pessimistic locking. Anyway, I don't think it's something you need to build yourself by any means: check the options on your db engine to see how to work with it. Commented Jan 9, 2018 at 19:11
  • The fact that your application is a desktop application (a fat client) doesn't make much difference. It can be designed in the same way as a highly-available, multi-instance server application. Commented Jan 16, 2018 at 7:06