To begin, I have read the FAQ and understand that SQLite wasn't
designed to be used over a network, accept all responsibility for data
loss, zombie armageddon, etc...
That said I am trying to determine if a bunch of sqlite DBs can be
successfully shared over the network using AFS (as an alternative to
NFS). We have a web app which works not unlike a traditional
multi-user unix environment, except that users work through a web
interface. Each user has their own sqlite database, and writes are
relatively infrequent to any single database.
On the OpenAFS mailing list, I was told that this might be problematic
because of the lack of support for byte-range locking in OpenAFS, but
that...
> However, my understanding that shared r/w access to sqlite
through AFS probably does work,
> provided you ensure sqlite uses the correct locking style (cf.
sqlite's os_unix.c):
>
> #define SQLITE_WHOLE_FILE_LOCKING 0x0001 /* Use whole-file locking */
>
> This feature is apparently due to Adam Megacz, who posted
briefly about it in 2006.
> See http://marc.info/?l=sqlite-users&m=116742195016159&w=2 .
(to quote Matt W. Benjamin).
I haven't found very much information on "whole-file locking" from
google, but did find this ancient thread:
http://www.mail-archive.com/sqlite-users@sqlite.org/msg17305.html
...but I'm not quite sure what to do with that. What is your take on
this, and how would I go about enabling "whole-file locking"? Thanks
for any insight.
Sincerely,
Brandon Simmons
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
