Using threads to make a nicer user interface is one thing. Performing
DB access from threads is another.
The point made is not that you should not use threads, it is to indicate
the cost of using threads. Windows is slow in creating processes
compared to Unix, but otherwise Windows processes behave much the same
as Unix ones with pipes, inherited handles etc.
Jonas Sandman wrote:
Well I am certainly a newbie in this context, threads must certainly
be used when writing Windows application since you are not at liberty
to splinter your process like you can on a *nix based system, no?
On 10/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
John Stanton <[EMAIL PROTECTED]> wrote:
When multi-processor machines are used thread usage may indeed implement
parallel processing when used appropriately and have tangible benefits.
True enough, in general. But with SQLite 3.5, access to each
database connection is serialized. So even though the interface
allows you to have 20 different threads all doing sqlite3_exec()
on the same connection at the same time, the SQL statements are
still being processed one by one, regardless of how many CPUs
you devote to the task.
--
D. Richard Hipp <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
