Re: [sqlite] idea: sqlite3_begin() and sqlite3_end() ?

[Eli Burke]

That's a good question. It would save all the wrapper writers some
time. I don't think the library is the place to put thread safe
code for several reasons:
Some of us don't use threads and don't need thread
safe code.
I prefer modular code with as little mixing of function
as possible. It makes it easier for me to reuse code in
other projects. (For example: Don't put GUI messagebox
code to report errors into sqlite. I might want to use it in
an mp3 player, which doesn't have a GUI.)
Since it's very operating system dependent it would
be difficult for Dr. Hipp to test. He doesn't have a copy of every
operating system and every version at his office. He probably
doesn't know how to write thread safe code on every OS either.
 

I don't think the discussion of adding sqlite_begin/end/rollback should 
get bogged down
with whether or not it should support threads. It's an idea that stands 
on its own merit.

Actually, come to think of it, each thread *should*  have it's own DB 
handle, and each
DB handle can use transactions independently of the others 
(IMMEDIATE/DEFERRED/
EXCLUSIVE notwithstanding). So really it's a non-issue. I shouldn't have 
mentioned it in
the first place :-)

-Eli