工作流程集成 - 数据层 [英] Workflow integration - Data tier

问题描述

嘿gals / guys，

Hey gals/guys,

推荐答案

您现有的应用程序数据库是否在SQL Server上运行？如果没有，单数据库方案实际上不是一个选项，因为WF只附带SQL Server持久性和跟踪提供程序。

您可能想要重新考虑参照完整性。我假设您的订单表和WF持久性表之间的参照完整性。在提交之前，请确保您了解Persistence表中工作流的生命周期。它可能要求您使您的应用程序的"创建订单"功能参与与工作流的第一个持久性操作相同的事务，这在实践中非常棘手。此外，当工作流程完成或终止时，它将从持久性数据库中删除，同时也会破坏您的外键链接。

确定是否要在应用程序模式中托管WF表可能只是个人喜好的问题。你已经掌握了利弊。我认为你提供对应用程序数据库模式的直接访问的任何人都可能也值得信赖，也可以访问工作流模式。

Is your existing application database running on SQL Server? If not, the one-database scenario isn't really an option because WF only comes with a SQL Server persistence and tracking provider.

You may want to rethink the referential integrity though. I am assuming you mean referential integrity between your order table and the WF persistence table. Make sure you understand the lifecycle of the workflow in the Persistence table before you commit to this. It may require you to make your application's "Create Order" functionality participate in the same transaction as the workflow's first persistence operation, which would be very tricky to do in practice. Also, when a workflow is completed or terminated, it is deleted from the persistence database, also breaking your foreign key link.

Deciding whether you want to host the WF tables in your application schema probably just comes down to a matter of personal preference. You've got a good handle on the pros and cons. I would think that anyone that you provide direct access to your application's database schema is probably also trustworthy enough to have access to the workflow schema as well.

这篇关于工作流程集成 - 数据层的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！