Christian Smith <[EMAIL PROTECTED]> wrote: > > > >3. Extend the sqlite3_open commands to support URI style path > >references in order to specify the file system locking type (as > >opposed to modifying the arguments list). After a little poking > >around on RFC 3986 <http://www.ietf.org/rfc/rfc3986.txt> I'm inclined > >to specify the locking choice via the query part of the URI. For > >example: > > > > file:///mounts/myhost/dbfile.db?locktype=flock > > file:///localdisk/otherdbfile.db?locktype=automatic > > > I'd be more inclined to add a PRAGMA. URIs are ugly and a pain to type in,
The reason for using a URI is so that you could specify the locking style for databases that you ATTACH. You are not required to use a URI - an ordinary filename will continue to work. You could, perhaps, set the default locking mechanism using a pragma. But it is important to be able to specify alternative locking mechanisms for ATTACHed databases. -- D. Richard Hipp <[EMAIL PROTECTED]>
