This is the mail archive of the
mailing list for the Cygwin project.
Re: [TEST] sqlite3-3.7.17-1 (Cygwin 1.7.19 locking feature)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 7 Jun 2013 10:03:37 +0200
- Subject: Re: [TEST] sqlite3-3.7.17-1 (Cygwin 1.7.19 locking feature)
- References: <51ACF886 dot 10301 at etr-usa dot com> <51AD3BB4 dot 2010601 at acm dot org> <20130604084128 dot GB19572 at calimero dot vinschen dot de> <20130604093749 dot GA32667 at calimero dot vinschen dot de> <51AF9A32 dot 2030706 at etr-usa dot com> <20130606172218 dot GD13320 at calimero dot vinschen dot de> <51B0DBCB dot 4010005 at etr-usa dot com>
- Reply-to: cygwin at cygwin dot com
On Jun 6 12:58, Warren Young wrote:
> On 6/6/2013 11:22, Corinna Vinschen wrote:
> >The lazy unlock request D tells the system to unlock all locks on the
> >entire file. This works fine with POSIX locks, but it does not work
> >with Windows locks. These require to unlock a lock exactly as it has
> >been created.
> I wouldn't be upset if you decided that was grounds for removing the
> code that tries to support mandatory locking for POSIX locks. As
> far as I'm concerned, this is very much an experimental feature, and
> experiments often fail. The failure already told us what to try
> next (BSD locks) and according to the one report received so far, it
> looks like it might fix it.
Well, after all it's still record locking, so it's kind of weird to
support a flock-like file lock but no record locks. If an application
uses this carefully with Windows semantics in mind, it might even be
However, what's missing in the long run is documentation. I'm just
about to add a few words to the docs.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple