您是否考虑过仅使用 XML 来存储数据？它没有比这更便携的了，只要您的客户端存储需求很简单，它就可以正常工作。例如，不需要存储大量的域对象。
此外，使用 XML 数据存储还可以解决许多设置和安装难题。您只需引用与可执行文件相关的一个或多个文件即可。您无需担心为各种平台安装数据库引擎，然后担心升级。
Have you considered just using XML to store the data? It doesn't get any more portable than that and will work fine as long your client-side storage needs are simple. E.g. not a large amount of many domain objects that need to be stored.
Additionally using an XML data store solves a lot of setup and installation headaches. You simply reference a file (or files) relative to your executable. You don't need to worry about installing db engines for a variety of platforms and then worry about upgrading.
发布评论
评论（3）
您是否考虑过仅使用 XML 来存储数据？它没有比这更便携的了，只要您的客户端存储需求很简单，它就可以正常工作。例如，不需要存储大量的域对象。
此外，使用 XML 数据存储还可以解决许多设置和安装难题。您只需引用与可执行文件相关的一个或多个文件即可。您无需担心为各种平台安装数据库引擎，然后担心升级。
Have you considered just using XML to store the data? It doesn't get any more portable than that and will work fine as long your client-side storage needs are simple. E.g. not a large amount of many domain objects that need to be stored.
Additionally using an XML data store solves a lot of setup and installation headaches. You simply reference a file (or files) relative to your executable. You don't need to worry about installing db engines for a variety of platforms and then worry about upgrading.
为每个进程提供自己的 sqlite3 数据库是否可行？无论如何，他们最终都会使用中央数据库，对吧？
WOuld it be feasible to give each process their own sqlite3 database? They all ultimately use the central database anyway, right?
看看 Firebird。
您可以将它用作嵌入式引擎，就像 SQLite 一样，但它也可以扩展到完整的服务器。
唯一的缺点就是文档比较乱
Have a look at Firebird.
You can use it as an embedded engine just like SQLite, but it can scale to a full blown server as well.
The only drawback is, that the documentation is a mess