"Stephen Chrzanowski" wrote...
For the fifth time. ;)
It's probably more like 6th or 7th. He he he he...
On Sun, Apr 14, 2013 at 2:28 PM, jic wrote:
"Roger Binns" wrote...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/04/13 14:55, jose isaias cabrera wrote:
Can this prob
For the fifth time. ;)
On Sun, Apr 14, 2013 at 2:28 PM, jic wrote:
> "Roger Binns" wrote...
>
>
> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 13/04/13 14:55, jose isaias cabrera wrote:
>>
>>> Can this problem also from a DB file shared via Windows Shared folder
>>>
>>
>> An
"Roger Binns" wrote...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/04/13 14:55, jose isaias cabrera wrote:
Can this problem also from a DB file shared via Windows Shared folder
An effective way to corrupt your data is to use a networked filesystem.
They do not provide the exact requi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/04/13 14:55, jose isaias cabrera wrote:
> Can this problem also from a DB file shared via Windows Shared folder
An effective way to corrupt your data is to use a networked filesystem.
They do not provide the exact required semantics as a local f
"D. Richard Hipp" said...
SQLite version 3.7.16.2 is now available on the SQLite website
http://www.sqlite.org/
The 3.7.16.2 patch release contains a two-character change in the Windows
OS interface that fixes a long-standing race condition that could lead to
database corruption. This bu
SQLite version 3.7.16.2 is now available on the SQLite website
http://www.sqlite.org/
The 3.7.16.2 patch release contains a two-character change in the Windows OS
interface that fixes a long-standing race condition that could lead to database
corruption. This bug has apparently existed in
6 matches
Mail list logo