Deepak Kaul said:
> 1. Calling sqlite_exec within my C++ program
Good for one-off statements, like DDL. If you have to generate the SQL
and deal with parameters though, this option is no good.
> 2. Calling sqlite_prepare, sqlite3_step and sqlite3_finalize within my
> C++ program
Best for mu
If your application runs the same SQL statements more than once, use
prepare, but this way
sqlite3_prepare
...
multiple
sqlite3_step
sqlite3_reset
at the end
sqlite3_finalize
Sqlite3_exec is just a wrapper around prepare, step, reset...
Deepak Kaul wrote:
Please rank the following scenarios considering speed, locks and
stability. I'm using sqlite in a C++ environment and running in a
single process and single threaded environment where SQL_BUSY should
occur minimally.
1. Calling sqlite_exec within my C++ program
2. Calli
Please rank the following scenarios considering speed, locks and
stability. I'm using sqlite in a C++ environment and running in a
single process and single threaded environment where SQL_BUSY should
occur minimally.
1. Calling sqlite_exec within my C++ program
2. Calling sqlite_prepare, sq
4 matches
Mail list logo
