同步框架触发器不会触发 [英] Sync framework trigger doesnt fire

查看:95
本文介绍了同步框架触发器不会触发的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好!

我在新配置的应用程序上遇到了麻烦.此应用程序连接到SQL Server 2005,并运行自定义C#代码.我已经编写了它,以便在用户端使用数据集和绑定对象,并且具有双向同步到服务器的Microsoft同步框架.

我尝试使用谷歌搜索的挑战是,偶尔在SQL Server表中未给新行赋予CreationDate,因此不会在整个用户之间进行同步.它在表上具有自动生成的触发器,该触发器是根据程序中的本地数据库缓存设置的.

我的问题是,我可以删除此触发器,而是确保客户端上的应用程序插入了CreationDate吗?
如果没有,我该如何解决这个问题?

为什么日期戳采用UTC日期格式?我看到了向用户显示LastEditDate的好处,但随后我需要时区的正确时间.

Hello people!

I have trouble with our newly configured application. This application is connected to a SQL server 2005, and runs custom C# code. I have written it to use datasets and bound object at the user end, and Microsoft sync framework with bidirectional sync to the server.

My challenge, which i have tried googling, is that occasionally a new row is not given a CreationDate at the SQL server table, and therefore is not synced throughout the users. It has the auto-generated triggers on the table, from set-up off local-database cache in the program.

My question is, can I remove this trigger, and instead make sure that CreationDate is inserted by the application on the client side?
If not, how can I work at this problem?

And why is the date stamp in format UTC date? I see benefits from showing the user the LastEditDate, but then I need the correct time for my time zone.

推荐答案

要删除触发器,请参见
For trigger removal see DROP TRIGGER[^].


这篇关于同步框架触发器不会触发的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆