【问题标题】:SqlException: procedure or function has too many arguments specifiedSqlException:过程或函数指定了太多参数
【发布时间】:2019-07-24 21:08:47
【问题描述】:

我在 SQL 方面的经验很少,我有一种方法可以访问数据库并将数据添加到几个不同的表中。我认为我的存储过程是正确的。这是我遇到问题的方法。

我正在创建一个 PUT 的 Web API 端点,它应该能够向多个会话添加多个假期和日期并更新数据库。

这是我目前拥有的,我需要做什么才能不出现异常?

private void SaveGlobalOrderDays(List<SessionInfoList> sessionList, List<Holiday> selectedOrderHolidays, List<Holiday> selectedHolidays, List<string> orderDays, List<string> noOrderDays)
{
    try
    {
        using (SqlCommand cmd = new SqlCommand())
        using (SqlConnection connection = new SqlConnection(ConnectionString))
        {
            cmd.CommandTimeout = 600;
            cmd.CommandText = "[dbo].[SaveGlobalOrderDays]"; 
            cmd.CommandType = CommandType.StoredProcedure;
            cmd.Connection = connection;

            foreach (SessionInfoList session in sessionList)
            {
                cmd.Parameters.Add("@SessionId", SqlDbType.Int).Value = session.SessionID;

                if (selectedOrderHolidays.Count > 0)
                {
                    foreach (Holiday holiday in selectedOrderHolidays)
                    {
                        string orderHolidays = string.Join(",", holiday.Name).Trim();
                        cmd.Parameters.Add("@HolidayName", SqlDbType.NVarChar).Value = orderHolidays; 
                    }                                
                }

                if (selectedHolidays.Count > 0)
                {
                    foreach (Holiday holiday in selectedHolidays)
                    {
                        string noOrderHolidays = string.Join(",", holiday.Name).Trim();
                        cmd.Parameters.Add("@SelectedHolidayName", SqlDbType.NVarChar).Value = noOrderHolidays; 
                    }                                
                }

                if (orderDays.Count > 0)
                {
                    foreach (string order in orderDays)
                    {
                        string od = string.Join(",",order).Trim();
                        cmd.Parameters.Add("@OrderDays", SqlDbType.NVarChar).Value = od; 
                    }                                
                }

                if (noOrderDays.Count > 0)
                {
                    foreach (string noOrder in noOrderDays)
                    {
                        string nod = string.Join(",",noOrder).Trim();
                        cmd.Parameters.Add("@NoOrderDays", SqlDbType.NVarChar).Value = nod; 
                    }                                
                }                                             
            }

            foreach (SqlParameter parameter in cmd.Parameters)
            {
                if (parameter.Value == null)
                    parameter.Value = DBNull.Value;
            }

            connection.Open();

            cmd.ExecuteNonQuery();

            cmd.Dispose();
        }
    }
    catch (Exception ex)
    {
        string message = "Failed to save global order info";
        // Logger.Error(LogSource, "SaveGlobalOrderDays", string.Empty, message, string.Empty, ex);
        throw new Exception(message, ex);
    }
}

存储过程:

IF OBJECT_ID('[dbo].[SaveGlobalOrderDays]') IS NOT NULL
     DROP PROCEDURE [dbo].[SaveGlobalOrderDays]
GO

CREATE PROCEDURE [dbo].[SaveGlobalOrderDays]
    @SessionId INT,
    @HolidayName NVARCHAR(MAX),
    @SelectedHolidayName NVARCHAR(MAX),
    @OrderDays NVARCHAR(MAX),
    @NoOrderDays NVARCHAR(MAX)
WITH ENCRYPTION
AS
BEGIN
    SET NOCOUNT ON;

    UPDATE [cfgSchedule]
    SET [cfgSchedule].[SessionId] = @SessionId,
        [OrderDays] = @OrderDays,
        [NoOrderDays] = @NoOrderDays
    FROM [cfgSchedule],[SessionHolidayMapping],[SessionOrderHolidayMapping]
    WHERE [cfgSchedule].[SessionId] = [SessionHolidayMapping].[SessionId]
      AND [cfgSchedule].[SessionId] = [SessionOrderHolidayMapping].[SessionId]
      AND [cfgSchedule].[SessionId] = @SessionId

    UPDATE [SessionHolidayMapping]
    SET [SessionHolidayMapping].[HolidayName] = @SelectedHolidayName
    FROM [cfgSchedule],[SessionHolidayMapping],[SessionOrderHolidayMapping]
    WHERE [cfgSchedule].[SessionId] = [SessionHolidayMapping].[SessionId]
      AND [cfgSchedule].[SessionId] = [SessionOrderHolidayMapping].[SessionId]
      AND [cfgSchedule].[SessionId] = @SessionId

    UPDATE [SessionOrderHolidayMapping]
    SET [SessionOrderHolidayMapping].[HolidayName] = @HolidayName
    FROM [cfgSchedule],[SessionHolidayMapping],[SessionOrderHolidayMapping]
    WHERE [cfgSchedule].[SessionId] = [SessionHolidayMapping].[SessionId]
      AND [cfgSchedule].[SessionId] = [SessionOrderHolidayMapping].[SessionId]
      AND [cfgSchedule].[SessionId] = @SessionId
END
GO  

【问题讨论】:

    标签: c# sql asp.net-core ado.net


    【解决方案1】:

    我们有这个循环:

    foreach (SessionInfoList session in sessionList)
    {
    

    在循环中,我们有这个参数:

    cmd.Parameters.Add("@SessionId", SqlDbType.Int).Value = session.SessionID;
    

    以及有条件的其他这些,它们也在循环内部:

    cmd.Parameters.Add("@NoOrderDays", SqlDbType.NVarChar).Value = nod; 
    cmd.Parameters.Add("@HolidayName", SqlDbType.NVarChar).Value = orderHolidays; 
    cmd.Parameters.Add("@SelectedHolidayName", SqlDbType.NVarChar).Value = noOrderHolidays; 
    cmd.Parameters.Add("@OrderDays", SqlDbType.NVarChar).Value = od; 
    

    这些循环尝试在每次迭代时重新添加新项目到 Parameters 集合,这意味着您将在其中任何一个第一次到达第二次迭代时获得错误数量的参数。

    此外,我们在循环的底部执行此操作:

    connection.Open();
    cmd.ExecuteNonQuery();
    cmd.Dispose();
    

    像这样的紧密循环是我们不必每次都重新创建和重新打开连接的一种情况。让我们这样做:

    private void SaveGlobalOrderDays(IEnumerable<SessionInfoList> sessionList, IEnumerable<Holiday> selectedOrderHolidays, IEnumerable<Holiday> selectedHolidays, IEnumerable<string> orderDays, IEnumerable<string> noOrderDays)
    {
        try
        {
            using (SqlConnection connection = new SqlConnection(ConnectionString))
            using (SqlCommand cmd = new SqlCommand("[dbo].[SaveGlobalOrderDays]", connection))
            {
                cmd.CommandTimeout = 600;
                cmd.CommandType = CommandType.StoredProcedure;
    
                //Set up parameter placeholders once, before any looping starts.
                // From here on out we'll only ever set their .Value properties.
                cmd.Parameters.Add("@SessionId", SqlDbType.Int);
                //Add a Length to these!
                // If the target columns really are nvarchar(max), use -1
                cmd.Parameters.Add("@HolidayName", SqlDbType.NVarChar, -1); 
                cmd.Parameters.Add("@SelectedHolidayName", SqlDbType.NVarChar, -1);
                cmd.Parameters.Add("@OrderDays", SqlDbType.NVarChar, -1);
                cmd.Parameters.Add("@NoOrderDays", SqlDbType.NVarChar, -1);
    
    
                //Open the connection just once, immediately before beginning of the loop.
                // The using block will ensure it is closed later.
                connection.Open(); 
                foreach (SessionInfoList session in sessionList)
                {
                    cmd.Parameters["@SessionId"].Value = session.SessionID;
    
                    cmd.Paramters["@HolidayName"].Value = DBNull.Value;
                    string joinedNames = string.Join(",", selectedOrderHolidays.Select(h => h.Name.Trim()));
                    if (!string.IsNullOrEmpty(joinedNames))
                        cmd.Paramters["@HolidayName"].Value = joinedNames;
    
                    cmd.Paramters["@SelectedHolidayName"].Value = DBNull.Value;
                    joinedNames = string.Join(",", selectedHolidays.Select(h => h.Name.Trim()));
                    if (!string.IsNullOrEmpty(orderHolidays))
                        cmd.Paramters["@SelectedHolidayName"].Value = joinedNames;
    
                    cmd.Paramters["@OrderDays"].Value = DBNull.Value;
                    joinedNames = string.Join(",", orderDays);
                    if (!string.IsNullOrEmpty(joinedNames))
                        cmd.Paramters["@OrderDays"].Value = joinedNames;
    
                    cmd.Paramters["@NoOrderDays"].Value = DBNull.Value;
                    joinedNames = string.Join(",", noOrderDays);
                    if (!string.IsNullOrEmpty(joinedNames))
                        cmd.Paramters["@NoOrderDays"].Value = joinedNames;
    
                    //Now there's no need to Open() or Dispose() anything at this point.
                    cmd.ExecuteNonQuery();
                }
            }
            // Consider using a separate Try/Catch inside the loop.
            // ... unless you want one failure to abort everything part way through, with some updates completed and some not.
            catch (Exception ex)
            {
                string message = "Failed to save global order info";
                // Logger.Error(LogSource, "SaveGlobalOrderDays", string.Empty, message, string.Empty, ex);
                throw new Exception(message, ex);
            }
        }
    

    最后,这看起来像是在各个列中设置逗号分隔值。这是非常糟糕的架构设计! 永远不要将逗号分隔的数据放在单个列中。将这些列放入其他表中可能会做得更好。

    【讨论】:

    • 我实际上确实需要将每个“selectedOrderHoliday”、“selectedHoliday”、“orderDays”和“noOrderDays”分开并放入它们指定的列中。这就是为什么我将这些值作为单独的实体作为参数传入的原因。不知道我在想什么,将它们重新连接在一起,作为一个用逗号分隔的字符串。我在制定一个好的方法时遇到了一些麻烦,有什么建议吗?
    • "I actually do need each [item] seperated and put into their assigned column." 不,你没有。你真的没有。你可以使用一个单独的来完成同样的事情,其中​​每一行都有来自当前表的主键,一个“类型”列告诉您正在查看的当前表中的哪个源序列,以及关联序列中的一个项目。因此,当前表中的补充表中会有更多行,但您保留了良好的规范化。
    • 谢谢!我不是故意要给人争论的感觉,但对这一切都是新手,我真的不知道我不知道什么。
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2021-02-20
    • 2019-05-28
    • 2019-10-07
    • 2013-11-07
    相关资源
    最近更新 更多