Given a multi-developer project using some sort of version control, and in which one part of the project would include using a desktop application in which the users would add real production data to a sqlite database file, which will then later be used as input/configuration data in an another application. How this file should be distributed between the developers? In version control? On a shared network drive?

You can also switch the sqlite to something else, the only requirement is that it should be embeddable in the desktop application.

有帮助吗?

解决方案

Sounds like you have distributed uses with local desktop applications, and you want to have them enter and save data into a shared database.

The client desktop applications can simply connect to a database server using TCP. You can't use Sqlite for this, as it is a file-based database and not a database server. You could use PostgreSql though.

Other options:

  1. local database server on each client computer that synchronizes with master databases or other client databases using replication. Generally speaking, these should all be the same "brand" of database.

  2. local file database on each client computer (such as sqlite) that synchronizes with master database or other client databases using a tool like SymmetricDS or Daffodil which lets you sync different databases over HTTP.

许可以下: CC-BY-SA归因
不隶属于 StackOverflow
scroll top