Thank you Joe, it works the way you suggested.
However its a little confusing since the parameter name is *not* required, it
fact even *not allowed* in case where there's no number following "?". In other
words, there are three distinct and mutually incompatible ways to specify a
parameter:
1) "?" - works ONLY without parameter name
2) "?1" - works ONLY with parameter name of "1" (without "?" prefix)
3) ":1" or "@1" - works ONLY with parameter name of ":1" or "@1" respectively
(includes the prefix)
I personally was trying to use positional parameters instead of named ones to
avoid paying the performance price for internal parameter name lookup. But
reading this makes me think that "?nnn" syntax relies on the name as well and
not the position and therefore does not carry any performance benefits. Is that
true?
Thanks again,
- Levi> From: sql...@mistachkin.com
> To: sqlite-users@sqlite.org
> Date: Fri, 3 Feb 2012 09:51:17 -0800
> Subject: Re: [sqlite] SQLite via ADO.NET provider: Insufficient parameters
> supplied to the command
>
>
> Levi Haskell wrote:
> >
> > command.Parameters.Add(new SQLiteParameter {Value = 1});
> > command.Parameters.Add(new SQLiteParameter {Value = 2});
> > command.Parameters.Add(new SQLiteParameter {Value = 3});
> > command.Parameters.Add(new SQLiteParameter {Value = 4});
> >
>
> Try this instead:
>
> command.Parameters.Add(new SQLiteParameter { ParameterName = "1", Value = 1
> });
> command.Parameters.Add(new SQLiteParameter { ParameterName = "2", Value = 2
> });
> command.Parameters.Add(new SQLiteParameter { ParameterName = "3", Value = 3
> });
> command.Parameters.Add(new SQLiteParameter { ParameterName = "4", Value = 4
> });
>
> --
> Joe Mistachkin
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
