[sqlite] sqlite3_create_function and threads

From the docs it's unclear to me whether the use of sqlite3_create_function is thread-specific or not. To put it another way, if I call sqlite3_create_function to install a custom function, is that function now available to all threads using SQLite or is it available only to the thread that

[sqlite] sqlite3_create_function and threads

Yes. What's wrong with that? Nothing at all - I just needed to know whether that was the case so I could design certain sections of my code accordingly. Thanks for the help! -- Paul Roberts ___ sqlite-users mailing list sqlite-users@sqlite.org

[sqlite] Balance between keeping DBs open vs repeated open/close

Thanks Stephan and Simon - I kind of figured it was one of those how long is a ball of string questions, but I just wanted to check there weren't any particular gotchas to watch out for. Regarding the separate files, it seems the best way to go. Each individual table could get pretty large

[sqlite] Balance between keeping DBs open vs repeated open/close

My application makes use of a number of separate SQLite DB files (in some cases 100). Each DB is handled by its own thread, which may be making frequent small writes, or sleeping extensively then occasionally making a more substantial number of writes. I'm trying to decide on a policy for