Lawrence D'Oliveiro schrieb:
In message , Steve
Holden wrote:
Yes, but not to MySQL, please. Particularly since there is a sword of
Damocles hanging over its head while the Oracle takeover of Sun is
pending.
Ah, I see the FUDsters are crawling out of the woodwork here, as well. I’ve
got new
Lawrence D'Oliveiro wrote:
> In message , Steve
> Holden wrote:
>
>> Yes, but not to MySQL, please. Particularly since there is a sword of
>> Damocles hanging over its head while the Oracle takeover of Sun is
>> pending.
>
> Ah, I see the FUDsters are crawling out of the woodwork here, as well.
In message , Steve
Holden wrote:
> Yes, but not to MySQL, please. Particularly since there is a sword of
> Damocles hanging over its head while the Oracle takeover of Sun is
> pending.
Ah, I see the FUDsters are crawling out of the woodwork here, as well. I’ve
got news for you: MySQL is an open
John Nagle wrote:
> pyt...@bdurham.com wrote:
>> I'm looking for the best practice way for a multi-threaded python web
>> server application to read/write to a shared file or a SQLite database.
>>
>> What do I need to do (if anything) to make sure my writes to a regular
>> file on disk or to a SQLi
pyt...@bdurham.com wrote:
I'm looking for the best practice way for a multi-threaded python web
server application to read/write to a shared file or a SQLite database.
What do I need to do (if anything) to make sure my writes to a regular
file on disk or to a SQLite database are atomic in nature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Diez B. Roggisch wrote:
> AFAIK, sqlite ensures process-serialization via locking, and threads
> synchronize themselves as well.
SQLite versions prior to 3.5 did not support using the same connection or
cursors in different threads. (You needed to al
pyt...@bdurham.com schrieb:
I'm looking for the best practice way for a multi-threaded python web
server application to read/write to a shared file or a SQLite database.
What do I need to do (if anything) to make sure my writes to a regular
file on disk or to a SQLite database are atomic in natu
I'm looking for the best practice way for a multi-threaded python web
server application to read/write to a shared file or a SQLite database.
What do I need to do (if anything) to make sure my writes to a regular
file on disk or to a SQLite database are atomic in nature when multiple
clients post
