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: David Rothenberger <daveroth at acm dot org>
- To: cygwin at cygwin dot com
- Date: Tue, 04 Jun 2013 08:25:27 -0700
- 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>
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
David Rothenberger ---- email@example.com
Kliban's First Law of Dining:
Never eat anything bigger than your head.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple