@Clemens: You wrote
"Not very much. But preparing a statement is very fast; don't try to be
too clever."
What do you mean with "don't try to be too clever"? Is preparing for
reuse not really necessary?
The select will be like "SELECT Value FROM RgbValues WHERE Object=? AND
Property=?".
Will it be better to prepare the sqlite3_stmt and reuse it? Or
ondemand: prepare, use and close the sqlite3_stmt. Is the
time-consuming of parsing a statement like above too high, so it will be
better to reuse the sqlite3_stmt (so i will have thousends prepared)?
Thx
heribert
heribert wrote:
The threads prepares their own sqlite3_stmt's with select statements
to the properties currently needed
A single statement "SELECT Value FROM T WHERE Name = ?" might suffice.
Is their any limitation of sqlite3_stmt bound to a database?
Only memory.
How much memory is used by a sqlite3_stmt?
Not very much. But preparing a statement is very fast; don't try to be
too clever.
Regards,
Clemens
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
