On 19 Oct 2011, at 11:20pm, Nico Williams wrote:
> On Wed, Oct 19, 2011 at 4:16 PM, Jay A. Kreibich wrote:
>> Just because the standards include such features, you seem to be
>> under the impression that every client and every server running on
>> top of any filesystem
On Wed, Oct 19, 2011 at 4:16 PM, Jay A. Kreibich wrote:
> On Wed, Oct 19, 2011 at 03:24:35PM -0500, Nico Williams scratched on the wall:
>> Also, regarding NFS, it would be safe to use if SQLite3 were to use
>> whole-file byte range locks. NFS makes concurrent access to byte
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/10/11 13:24, Nico Williams wrote:
> That explains why concurrent access over NFS or CIFS is dangerous. It
> doesn't explain that it's not possible to use SQLite3 over NFS or
> CIFS.
The simple answer is that they don't provide *exactly* the
On Wed, Oct 19, 2011 at 03:24:35PM -0500, Nico Williams scratched on the wall:
> On Wed, Oct 19, 2011 at 2:23 PM, Jay A. Kreibich wrote:
> > On Wed, Oct 19, 2011 at 02:13:35PM -0500, Nico Williams scratched on the
> > wall:
> >> On Wed, Oct 19, 2011 at 4:00 AM, Stephan Beal
On Wed, Oct 19, 2011 at 2:23 PM, Jay A. Kreibich wrote:
> On Wed, Oct 19, 2011 at 02:13:35PM -0500, Nico Williams scratched on the wall:
>> On Wed, Oct 19, 2011 at 4:00 AM, Stephan Beal wrote:
>> > On Tue, Oct 18, 2011 at 12:37 PM, Sune Ahlgren
>> >
On Wed, Oct 19, 2011 at 9:40 PM, Simon Slavin wrote:
> Think is, it's possible to do it right. It's just that doing it right
> means every operation takes two or three times as long as the slightly buggy
> implementations we have now. And people prefer fast-but-buggy.
>
On 19 Oct 2011, at 8:26pm, Stephan Beal wrote:
> On Wed, Oct 19, 2011 at 9:23 PM, Stephan Beal wrote:
>
>> race conditions, unclean network connection errors, blah blah blah. That
>> goes for all applications, not just databases.
>
> And not just for CIFS, but NFS and
On Wed, Oct 19, 2011 at 9:23 PM, Stephan Beal wrote:
> race conditions, unclean network connection errors, blah blah blah. That
> goes for all applications, not just databases.
>
>
And not just for CIFS, but NFS and other networked filesystems as well. i'm
not personally
On Wed, Oct 19, 2011 at 9:13 PM, Nico Williams wrote:
> > Nothing. Even MS Access cannot (or could not way back when i used it) be
> > safely used on SMB/CIFS storage.
>
> Can you elaborate as to why?
>
>
i unfortunately can't, except to say that file locking on networked
On Wed, Oct 19, 2011 at 02:13:35PM -0500, Nico Williams scratched on the wall:
> On Wed, Oct 19, 2011 at 4:00 AM, Stephan Beal wrote:
> > On Tue, Oct 18, 2011 at 12:37 PM, Sune Ahlgren
> > wrote:
> >> What can I do to make SQLite run safely on
On Wed, Oct 19, 2011 at 4:00 AM, Stephan Beal wrote:
> On Tue, Oct 18, 2011 at 12:37 PM, Sune Ahlgren
> wrote:
>> What can I do to make SQLite run safely on CIFS?
>
> Nothing. Even MS Access cannot (or could not way back when i used it) be
>
On Tue, Oct 18, 2011 at 12:37 PM, Sune Ahlgren wrote:
> What can I do to make SQLite run safely on CIFS?
>
Nothing. Even MS Access cannot (or could not way back when i used it) be
safely used on SMB/CIFS storage.
--
- stephan beal
2011/10/18 Sune Ahlgren :
> What can I do to make SQLite run safely on CIFS?
> /Sune
Do not use SQLite on shared device. Use client/server database or
client/server front-end of SQLite.
--
Kit
___
sqlite-users mailing list
Hi,
I have mounted a CIFS share like this (cat /proc/mounts)://192.168.0.1/test2
/var/spool/storage/Share cifs
rw,relatime,unc=\\192.168.0.1\test2,username=sune,uid=123,forceuid,gid=123,forcegid,addr=192.168.0.1,file_mode=0770,dir_mode=0770,nobrl,rsize=16384,wsize=114688
0 0
My CIFS options (
14 matches
Mail list logo