Re: sqlite defect
On 7/12/2013 12:49, fger...@gmx.de wrote: But since 3.7.17-3 I cannot read my databases any more unable to open datase file. Without a test case, debugging this will amount to testing guesses. My first guess: try setting the new CYGWIN_SQLITE_LOCKING environment variable to posix. That can fix it if you are trying to use two or more Cygwin SQLite based programs to access a single database file. The default mode for Cygwin SQLite is now -- and pretty much always has been -- to prefer allowing a single Cygwin SQLite program to cooperate with any number of native Windows programs for access to a single SQLite DB file. This means that in this posix mode, Cygwin SQLite is no longer likely to cooperate with native Windows SQLite based programs for access to a shared DB file. That's the tradeoff: choose to share with other Cygwin programs, or choose to share with native Windows programs. I remember there was a discussion on the cygwin general mailing list about this problem (backslashes in path?). If that's what's going on, my .17-3 build should have fixed the problem, not manifested it.
Aw: Re: sqlite defect
Von: Warren Young war...@etr-usa.com But since 3.7.17-3 I cannot read my databases any more unable to open datase file. Without a test case, debugging this will amount to testing guesses. It was with several different files, Mozilla sqlite bookmark database, and with SVN downloads (could not checkout any more). I saw this on several different machines, WinXP and Win7. Maybe the SVN problem was with the downgraded version, because SVN was not compatible with this one. My first guess: try setting the new CYGWIN_SQLITE_LOCKING environment variable to posix. That can fix it if you are trying to use two or more Cygwin SQLite based programs to access a single database file. Thanks. That's it. With this setting it works. Why isn't it the default? There was no concurrent access, just a single query with Cygwin. But I copied the mozilla places.sqlite bookmarks file to a backup directory first and wanted to extract the Links to a simple ASCII style. Does the sqlite file contain a locking flag inside? With the old version I never had a problem to access the files. Im not so familiar with sqlite, but I'm happy now that it works again. Thanks for your help!
Re: sqlite defect
Why was this thread redirected to cygwin-apps? cgf On Wed, Jul 17, 2013 at 02:52:11PM -0600, Warren Young wrote: On 7/12/2013 12:49, fger...@gmx.de wrote: But since 3.7.17-3 I cannot read my databases any more unable to open datase file. Without a test case, debugging this will amount to testing guesses. My first guess: try setting the new CYGWIN_SQLITE_LOCKING environment variable to posix. That can fix it if you are trying to use two or more Cygwin SQLite based programs to access a single database file. The default mode for Cygwin SQLite is now -- and pretty much always has been -- to prefer allowing a single Cygwin SQLite program to cooperate with any number of native Windows programs for access to a single SQLite DB file. This means that in this posix mode, Cygwin SQLite is no longer likely to cooperate with native Windows SQLite based programs for access to a shared DB file. That's the tradeoff: choose to share with other Cygwin programs, or choose to share with native Windows programs. I remember there was a discussion on the cygwin general mailing list about this problem (backslashes in path?). If that's what's going on, my .17-3 build should have fixed the problem, not manifested it.
Re: sqlite defect
On 7/17/2013 18:27, Christopher Faylor wrote: Why was this thread redirected to cygwin-apps? The thread started here, and I replied here. David Rothenberger tried to redirect it to the main list.
sqlite defect
I never had problems with sqlite before. But since 3.7.17-3 I cannot read my databases any more unable to open datase file. I remember there was a discussion on the cygwin general mailing list about this problem (backslashes in path?). The same behaviour on several of my machines (WinXP and Win7 64). The 64-bit version apparently works (maybe one crash). The previous version 3.7.16.2-1 was Ok. When I downgrade to this one in the Cygwin installer, sqlite works correctly again. Unfortunately I can't check out SVN any more, because there is a sqlite version mismatch with the SVN installation. Is there a solution for this bug. Or could you switch back to the working version again, with all the dependencies, as a workaround? sqlite is very essential, especially for SVN to work.
