On 22 Apr 2012, at 1:55pm, 田晶 wrote:
> Is there any temp solutions for this case? As we need some time to change our
> plan on this,thanks!
Don't do multi-user, multi-process, or multi-thread access for a file accessed
using NFS.
It is not possible for the SQLite team to fix this: the thing
On Sun, 22 Apr 2012 02:36:24 +, ?? wrote:
> I using the -o nolock option when I mount nfs storage,
> and it works, but I am not sure what will cause by this option in future...
In that case database corruption will occur if you happen to update
(insert, update, delete rows) the database from
On 21 Apr 2012, at 7:05pm, Kit wrote:
> 2012/4/21 田晶 :
>> Hi all,
>> I have a question when using sqlite on redhat6, I put the sqlite file on nfs
>> storage(this storage is shared by isilion), the client using redhat 6 x64.
>> Tianjing
>
> Never use SQLite on NFS storage.
Slightly longer answ
2012/4/21 田晶 :
> Hi all,
> I have a question when using sqlite on redhat6, I put the sqlite file on nfs
> storage(this storage is shared by isilion), the client using redhat 6 x64.
> Tianjing
Never use SQLite on NFS storage.
--
Kit
___
sqlite-users mai
Hi all,
I have a question when using sqlite on redhat6, I put the sqlite file on nfs
storage(this storage is shared by isilion), the client using redhat 6 x64.
When I search the database, I got the following error:
[root@3-1 yubiao]# sqlite3 .UPLOAD.db
SQLite version 3.6.20
Enter ".help" for in
5 matches
Mail list logo
