You shouldn't access a SQLite database remotely, except maybe for read only access, but that could come under fire. Any network file action can't guarantee that write locks happen.
If you attempt to access a file in READ-ONLY mode, you'll be greeted with a 1-5 second delay (I don't remember what the delay is right now) per connection. If you're using one connection to the DB, then you'll experience the delay. If you've got one connection going for the life of your application, you'll get hit with the first delay, but all subsequent queries will work. On Thu, May 22, 2014 at 8:12 AM, Hadashi, Rinat <rinat.hada...@intel.com>wrote: > Hi > > The first time I access a database takes significantly more time than > subsequent accesses. > I am looking for ideas to shorten the time required for the first access. > > I work on Linux, my db. file is "somewhere" in the file system, not > locally on the machine from which I am running sqlite3 > > Thanks > > Rinat Hadashi > > > --------------------------------------------------------------------- > Intel Israel (74) Limited > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
