On 6/6/2013 16:10, David Stacey wrote:
Thanks to Warren and Corinna for their considerable effort in getting
this working.
Thank you, Davids, for your testing. :)
I'm now nervously considering RFU'ing a -3 version, differing only in
removing the "posixmand" stuff. You'll have two choices on
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
On 05/06/13 23:27, David Rothenberger wrote:
On 6/5/2013 12:50 PM, Warren Young wrote:
The CYGWIN_SQLITE_LOCKING variable now has three possible states:
CYGWIN_SQLITE_LOCKING=posix -- same as before
CYGWIN_SQLITE_LOCKING=posixmand -- equivalent to leaving it undefined in
the 3.7.17-1 build
C
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 d
Corinna Vinschen writes:
> In theory this scenario could be worked around in Cygwin by bookkeeping
> the present locks, plus a piece of code which unlocks all existing locks
> in the given range when a lock or unlock request is coming in. However,
> the really dismal fact is, that an unlock before
On Jun 5 14:06, Warren Young wrote:
> On 6/4/2013 03:37, Corinna Vinschen wrote:
> >
> >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.
>
> SQLite locking is a hairball. It is spread ove
On 6/5/2013 16:27, David Rothenberger wrote:
I think the "AnythingElse" setting is what you intended for Subversion
users that want to interoperate with Windows?
Yes, though there is a chance that my SQL STC will clue someone into the
needed fix for posixmand mode so SQLite can work in this ro
On 6/5/2013 12:50 PM, Warren Young wrote:
> It required a spelunking expedition, complete with yak wagons and a team
> of five sherpas, one of which had to be left behind with a broken leg,
> but I figured out how to compile in the BSD locking VFS without
> disabling the POSIX one, then how to make
On 6/5/2013 13:22, Achim Gratz wrote:
David Rothenberger writes:
The good news is that the test cases that relied on temporary tables are
now passing.
Yes, but that is unrelated to the locking.
I was assuming that the switch from disk-based temp tables to in-memory
temp tables helped beca
On 6/4/2013 03:37, Corinna Vinschen wrote:
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.
SQLite locking is a hairball. It is spread over a range of about 2.5
kLOC within the 140 kLOC sql
On 6/4/2013 02:41, Corinna Vinschen wrote:
On Jun 3 17:58, David Rothenberger wrote:
... 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? The
Warren Young writes:
> 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
>
I'll try to free some time on the weekend for testing.
David Rothenberger writes:
> ... 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.
This is in all likelihood a good
On 04/06/13 01:58, David Rothenberger wrote:
... 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.
It appears that much water has already passed under the proverbial
bridge
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
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
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 Wind
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 Wind
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 eff
On 6/3/2013 5:58 PM, David Rothenberger wrote:
> I'll try the 1.7.10 test suite shortly and report back on the results,
> although I expect them to be the same.
Confirmed. And I get problems in practice using subversion without
setting the locking mode to posix.
--
David Rothenberger dave
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
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
22 matches
Mail list logo
