<p>From the sqlite documentation he quoted, it appears that ANY network filesystem, local or otherwise, should be avoided.</p>
<div class="gmail_quote">On Aug 27, 2012 8:13 PM, <<a href="mailto:bruceg113355@gmail.com">bruceg113355@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Monday, August 27, 2012 10:32:47 PM UTC-4, Bryan wrote:<br>
> bruceg113 wrote:<br>
><br>
> > I selected sqlite for the following reasons:<br>
><br>
> ><br>
><br>
> > 1) Ships with Python.<br>
><br>
> > 2) Familiar with Python.<br>
><br>
> > 3) The Sqlite description athttp://<a href="http://www.sqlite.org/whentouse.htmlappears" target="_blank">www.sqlite.org/whentouse.htmlappears</a> to meet my requirements:<br>
><br>
> > Very low volume and concurrency, small datasets, simple to use.<br>
><br>
><br>
><br>
> All good reasons, but a database file on a network drive is<br>
><br>
> contraindication for SQLite. A Google site-specific search<br>
><br>
> for "network" on <a href="http://www.sqlite.org" target="_blank">www.sqlite.org</a>, finds such warnings as:<br>
><br>
><br>
><br>
> "We have received reports of implementations of both Windows network<br>
><br>
> filesystems and NFS in which locking was subtly broken. We can not<br>
><br>
> verify these reports, but as locking is difficult to get right on a<br>
><br>
> network filesystem we have no reason to doubt them. You are advised to<br>
><br>
> avoid using SQLite on a network filesystem in the first place, since<br>
><br>
> performance will be slow."<br>
><br>
><br>
><br>
> That said, I don't know where your 17 seconds is going.<br>
><br>
><br>
><br>
> -Bryan<br>
<br>
Bryan,<br>
<br>
Thank you for your reply.<br>
Are you saying having a sqlite database file on a shared LOCAL network drive is problematic?<br>
<br>
Bruce<br>
--<br>
<a href="http://mail.python.org/mailman/listinfo/python-list" target="_blank">http://mail.python.org/mailman/listinfo/python-list</a><br>
</blockquote></div>