SMO Scripting - Missing regular property NotForReplication property bag state Lazy for type Trigger

未关闭
#198 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
csharp, sql
领域
databases

调研方向

检查 src/Microsoft/SqlServer/Management/SqlEnum/xml/trigger.xml 的第 66-68 行，并将 NotForReplication 字段与周围字段进行比较。跟踪在启用 ScriptingOptions.Triggers 时其模式如何影响预取；完成标准是为表编写脚本时不再因该字段查询数据库。

由索引模型根据 Issue 内容生成。

描述

Not doing anything fancy, just scripting out tables with ScriptingOptions.Triggers enabled.

Prefetch grabs nearly everything, except for the NotForReplication field it seems. When trying to script out a table with triggers enabled, it still reaches out to the database to grab this field.

No idea if it's relevant as I have no clue how these files are structured/used (other than for generating the prefetch query), but maybe it has something to do with how it's configured in this file?

https://github.com/microsoft/sqlmanagementobjects/blob/17b6e3235f4a7267c920a79685ae1e8941961e92/src/Microsoft/SqlServer/Management/SqlEnum/xml/trigger.xml#L66-L68

I noticed for some reason its mode is set to deploy instead of design like the other fields. Might have nothing to do with it, but figured I would point it out in case it's helpful.

主要语言
C#
星标
143
派生
28
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/sqlmanagementobjects 的其他 Issue

查看 microsoft/sqlmanagementobjects 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。