Lee Crain <[EMAIL PROTECTED]> wrote:
Why is it "highly recommended" to use the function call sequence you
iterate in preference to the sqlite3_exe call, since it is implemented
using that sequence?
1) It's usually easier to write a loop, than to break out the body of
the loop into a separate c
Finishing the COMMIT releases the file locks.
Rich Rattanni wrote:
I hope it isnt too wierd to reply to your own posts I just wanted
to follow up with I found the following post: "[SQLITE] thread
concurrency, inserts using transactions, bug?" The problem is multiple
begins causing deadlock,
I hope it isnt too wierd to reply to your own posts I just wanted
to follow up with I found the following post: "[SQLITE] thread
concurrency, inserts using transactions, bug?" The problem is multiple
begins causing deadlock, and drh suggests using "BEGIN IMMEDIATE" and
dealing with SQLITE_BUSY'
On 9/4/06, Cesar David Rodas Maldonado <[EMAIL PROTECTED]> wrote:
What i meaning how sqlite do for search b-tree indexs? the index are copy to
main memory or the merge is done just in hard disk search for every item?
understand my question?
Sqlite indexes may be cached by the operating system
What i meaning how sqlite do for search b-tree indexs? the index are copy to
main memory or the merge is done just in hard disk search for every item?
understand my question?
On 9/4/06, Cesar David Rodas Maldonado <[EMAIL PROTECTED]> wrote:
Hello to all!
I am developing a application for grea
5 matches
Mail list logo
