StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In MSDN it is explicitly stated that you cannot name the parameters which is the only way to "tell the ODBC command which parameter is which".</p> <p>Although the documentation can generate a bit of confusion:</p> <p>From <a href="http://msdn.microsoft.com/en-us/library/system.data.odbc.odbcparameter.aspx" rel="noreferrer">MSDN, OdbcParameter Class</a>:</p> <blockquote> <p>When CommandType is set to Text, the .NET Framework Data Provider for ODBC does not support passing named parameters to an SQL statement or to a stored procedure called by an OdbcCommand. In either of these cases, use the question mark (?) placeholder.</p> </blockquote> <blockquote> <p>The order in which OdbcParameter objects are added to the OdbcParameterCollection must directly correspond to the position of the question mark placeholder for the parameter in the command text.</p> </blockquote> <p>From the above it seems to suggest that when CommandType is not set to Text maybe you can use named parameters, but unfortunately you can't:</p> <p>From <a href="http://msdn.microsoft.com/en-us/library/system.data.odbc.odbccommand.commandtype.aspx" rel="noreferrer">MSDN, OdbcCommand.CommandType Property</a>:</p> <blockquote> <p>When the CommandType property is set to StoredProcedure, you should set the CommandText property to the full ODBC call syntax. The command then executes this stored procedure when you call one of the Execute methods (for example, ExecuteReader or ExecuteNonQuery).</p> </blockquote> <blockquote> <p>The .NET Framework Data Provider for ODBC does not support passing named parameters to an SQL statement or to a stored procedure called by an OdbcCommand. In either of these cases, use the question mark (?) placeholder...</p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload