I tested this using the following stored procedure in SQL Server 2008 R2:
CREATE PROCEDURE [dbo].[breakfast]
@person varchar(50) = 'nobody',
@food varchar(50) = 'tofu'
AS
BEGIN
SET NOCOUNT ON;
SELECT @person + ' likes to eat ' + @food
END
The Bad News ("CALL")
I found that
sql = """
{ CALL breakfast (@food=?, @person=?) }
"""
params = ('bacon','Gord')
crsr.execute(sql, params)
gave inconsistent results.
With the {SQL Server Native Client 10.0}
ODBC driver it ignored the parameter names and treated the parameters as positional, yielding ...
bacon likes to eat Gord
... and with the older {SQL Server}
ODBC driver I just got the error
DataError: ('22018', '[22018] [Microsoft][ODBC SQL Server Driver]Invalid character value for cast specification (0) (SQLExecDirectW)')
The Good News ("EXEC")
I found that
sql = """
EXEC breakfast @food=?, @person=?
"""
params = ('bacon','Gord')
crsr.execute(sql, params)
gave me the following (correct) result using both ODBC drivers
Gord likes to eat bacon
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…