This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [TEST] sqlite3-3.7.17-1 (Cygwin 1.7.19 locking feature)

On Jun  4 08:25, David Rothenberger wrote:
> On 6/4/2013 2:37 AM, Corinna Vinschen wrote:
> > On Jun  4 10:41, Corinna Vinschen wrote:
> >> On Jun  3 17:58, David Rothenberger wrote:
> >>> On 6/3/2013 1:11 PM, Warren Young wrote:
> >>>> This is a big-push attempt at a version of Cygwin SQLite that will make
> >>>> everyone happy (ha!) whether they want POSIX advisory locking behavior
> >>>> or Windows mandatory locking behavior.  My part of the effort is being
> >>>> stubborn on this point and doing the basic testing and packaging.  The
> >>>> real magic was added by Corinna to yesterday's 1.7.19 cygwin1.dll snapshot.
> >>> [...]
> >>> ... initial results with the Subversion test suite (for 1.8.0-rc2) show
> >>> that most tests fail with a "sqlite: database is locked (S5)" error
> >>> unless CYGWIN_SQLITE_LOCKING=posix.
> >>
> >> The question now is: Why?
> > 
> > IOW: It would be nice to have a simple testcase (plain C, only Cygwin
> > POSIX calls, self-contained, yada yada) to see what sqlite expects in
> > POSIX lock mode.
> This may take some time or be completely over my head given all the
> layers involved with the Subversion test suite (python bindings,
> subversion code, libapr1). I probably won't get to it for a few days or
> longer.

Thanks for the offer.  But really, it's not at all pressing, since it
would probably be mainly for curiosity.  There's just no way to improve
Windows locking.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]