Hi again,
Actually it seems that the database file needs read-only (444) permissions
for the feature to work.
We did it also and I still get the same error.
I am checking at the source code from Google and it's not clear enough still
to know what do to :
Thanks Richard,
According to the source code, it's an experimental feature :
/* The following is VERY experimental */
{ "writable_schema", SQLITE_WriteSchema },
{ "omit_readlock",SQLITE_NoReadlock},
We have tested today and it does seem to work. The
> PRAGMA omit_readlock=ON;
>
Hm, should be documented, no?
I could use that as well...
Just wondering if this has any speed advantages?
--
Christophe Leske
www.multimedial.de - [EMAIL PROTECTED]
http://www.linkedin.com/in/multimedial
Lessingstr. 5 - 40227 Duesseldorf - Germany
0211 261 32
On Nov 19, 2008, at 5:07 AM, David Levy wrote:
> Is there a way to tell Sqlite to not lock the database when we know
> there
> are only read-only queries ?
>
PRAGMA omit_readlock=ON;
D. Richard Hipp
[EMAIL PROTECTED]
___
sqlite-users mailing
Hi all,
I am experiencing a pretty annoying issue with my Sqlite3 databases.
I am using PDO to access small ( approx. 300Kb ) databases stored on an NFS
v3 mount. These queries are multithreaded as they come from a web
application. However, there are only SELECT statements, not any
5 matches
Mail list logo