And it's convenient to be able to do the prepare during startup. I've
just never had to worry about this situation. It means you have to do
special handling for the first _step, but it's a reasonably compact
way of handling the potential problem.
I can't use prepared statements in practice with the (interpreted)
scripting language I use most (AutoIt) due to its DLL invokation being
so slow: having to first prepare then perform multiple _Bind calls and
having to sort out variable type for each _Bind proves way slower than
an all-in-one "dumb" _Exec. That's possibly true for more scripting
languages.
That's why _Exec should definitely be kept part of the SQLite API.
Anyway, I expect things in this language could change in some future
and prepared statements become affordable in this context.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
