You should note that you're not using the SQLite C Interface and instead using the wrapper provided by System.Data.SQLite.org
If performance is critical to your scenario, you should use sqlite3_bind_* functions or their equivalents in the wrapper, without having to ask SQLite what parameter is mapped to which index. If you take on the ask of mapping parameter names to indices, you should strive to do it in a manner where you can cache it otherwise you'll run into the same performance issues you're trying to avoid with the current wrapper. Finally, please include at least some code snippets or steps to help understand your problem better. On Fri, Jul 17, 2015 at 9:21 AM, Hayden Livingston <halivingston at gmail.com> wrote: > In my program I'm spending most of my time in this function: > > System.Data.SQLite!SQLiteStatement.MapParameter > > This function is doing string comparisons to map the correct parameter. > > I do put my SQL command text into a statement and prepare it. I was > wondering if there is a way to do so for my parameters also. Obviously > parameters vary, so it'd be nice to have a parameterized function? > > Or is that essentially what a stored procedure is? > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
