Stored procedure receives multiple parameter problems Master invited

lina723

Upstairs, can you get the full line of code? ? ? ? ? Stop talking about ideas! !! !! !!

mgs_pexp

Yeah ~! !! !! !! !! What I want is code, not ideas

cihcihxxc

just for reference

CREATE PROCEDURE Test
    @idString NVARCHAR (1000) // If its value is 1,2,3,4,6,7,8
AS
    DECLARE @sql NVARCHAR (2000)

    SET @sql = 'UPDATE Images SET [Name] = `` Test' 'WHERE ID IN (' + @idStrings + ')'

    exec @sql


@idStrings is a combination of the above from your code in the form:
    imgeid1, imageid2, imageid3

The premise ID field must be an integer (such as int, bigint)

looser_01

The string @idString cannot end with ",", that is, it cannot be "1,2,3,4,6,7,8,", it should be "1,2,3,4,6,7,8"

pupupu01

Let's put it this way: I combined the selected image IDs into a string in the background of the page, separated by commas, such as: "1,2,3,4,6,7,8,"
This is passed to the stored procedure. The stored procedure splits the string of IDs, and then the name field is "tested" based on these IDs.
How to write specific stored procedures
-------------------------------------------------- ---
@ s = "1,2,3,4,6,7,8"

update YourTable set name = 'Test' where charindex (',' + rtrim (id) + ',', ',' + @ s + ',')> 0

mgs_pexp

SET @sql = 'UPDATE Images SET [Name] = `` Test' 'WHERE ID IN (' + @idStrings + ')'

Where did @idStrings come from? ? ? ? ? ? Wrong?

looser_01

After string combination, Trim (',') can be used for preprocessing, and it cannot be empty "" at the same time, the judgment can be added during storage.
if (@idString <> '')
begin
    DECLARE @sql NVARCHAR (2000)

    SET @sql = 'UPDATE Images SET [Name] = `` Test' 'WHERE ID IN (' + @idStrings + ')'

    exec @sql
end

xwgjyhl

where id in (your string)
I usually do this. You use "," to add the id together, and then execute it in SQL.

cihcihxxc

SET @sql = 'UPDATE Images SET [Name] = `` Test' 'WHERE ID IN (' + @idStrings + ')'

Where did @idStrings come from? ? ? ? ? ? Wrong?

==================
No, it's the parameters that your program passes to the stored procedure.

cihcihxxc

Exec @sql changed to exec (@sql)