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 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 SQLite switch between them at
> runtime.  (This is what gives me hope for Plan C, above.)

Thanks again for all your effort here.

> 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
> 
> CYGWIN_SQLITE_LOCKING=AnythingElse -- BSD flock() based mandatory locking.

I think the "AnythingElse" setting is what you intended for Subversion
users that want to interoperate with Windows?

The Subversion test suite passes with that setting. I don't know about
issues with TortoiseSVN since I don't use it personally.

-- 
David Rothenberger  ----  daveroth@acm.org

"Experience has proved that some people indeed know everything."
                -- Russell Baker

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


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