我最近遇到了 Nhibernate 生成的 SQL 的性能问题,如中所述
我还找到了一个链接,描述了来自唯一的 Jeff Atwood 的类似经历
http://legeronline.blogspot.ca/2009/03/evils-of-slow-paramaterized-query-plans.html
有谁知道是否有向 Nhibernate 添加“优化未知”选项?
我最近遇到了 Nhibernate 生成的 SQL 的性能问题,如中所述
我还找到了一个链接,描述了来自唯一的 Jeff Atwood 的类似经历
http://legeronline.blogspot.ca/2009/03/evils-of-slow-paramaterized-query-plans.html
有谁知道是否有向 Nhibernate 添加“优化未知”选项?
This example is a little more verbose:
public class OptionInterceptor: EmptyInterceptor
{
public override SqlString OnPrepareStatement(SqlString sql)
{
var parameters = sql.GetParameters();
var paramCount = parameters.Count();
if (paramCount == 0)
return sql;
string optionString = " OPTION (OPTIMIZE FOR (";
for (var i = 0; i < paramCount; i++)
{
var comma = i > 0 ? "," : string.Empty;
optionString = optionString + comma + "@p" + i + " UNKNOWN";
}
optionString = optionString + "))";
var builder = new SqlStringBuilder(sql);
builder.Add(optionString);
return builder.ToSqlString();
}
}
Then in your sessionfactory/initializer:
configuration.ExposeConfiguration(x =>
{
x.SetInterceptor(new OptionInterceptor());
});
ExecuteReader()
调用时添加提示