Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

2013/12/17 margave : > Well, I gave up on sqlite inside of Cygwin. > > I found a standalone sqlite3.exe that does not depend upon (or install with) > Cygwin. > It's from http://www.sqlite.org > One executable, no .dlls ... and it just runs, no problems. I think I know what's

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

2013/12/17 margave : > Well, I gave up on sqlite inside of Cygwin. > > I found a standalone sqlite3.exe that does not depend upon (or install with) > Cygwin. > It's from http://www.sqlite.org > One executable, no .dlls ... and it just runs, no problems. For most situation,

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

Well, I gave up on sqlite inside of Cygwin. I found a standalone sqlite3.exe that does not depend upon (or install with) Cygwin. It's from http://www.sqlite.org One executable, no .dlls ... and it just runs, no problems. -- View this message in context:

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On Sun, 15 Dec 2013 07:28:52 -0800 (PST), margave wrote: >Addendum: I ran "file" on sqlite3.exe ... > >On computer B (where sqlite3 works): PE32 executable (console) Intel 80386, >for MS Windows >On computer A (where it does not): PE32+ executable (console) x86-64, for >MS

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

2013/12/15 margave : > I noticed that the sqlite3.exe file on computer A has a different cksum than > the one on computer B. (Seems odd! The Cygwin installer shows the same > version on both!) Which version? SQLite 3.8.2-2? Apparently, you are running Cygwin on A and Cygwin64 on

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

Addendum: I ran "file" on sqlite3.exe ... On computer B (where sqlite3 works): PE32 executable (console) Intel 80386, for MS Windows On computer A (where it does not): PE32+ executable (console) x86-64, for MS Windows -- View this message in context:

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

I have the same problem. I have .sqlite db files, and I wish to read them with sqlite3.exe (under Cygwin x64 on Win 7 x64). I want this to work on both computer A and computer B. (Both have the same Win 7 and Cygwin installed). But it only works on computer B, not on computer A. I have the SAME

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On 6/9/2013 05:21, Stephen Chrzanowski wrote: Warren, when you say "we may be switching the official builds back to Unix mode soon", you're referring only to the Cygwin builds, correct? Of course. The Win32 versions will still be generated as is? I only maintain the Cygwin packages. I

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On 6/9/2013 07:42, Philip Goetz wrote: /path/to/sqlite3.exe db.sqlite on the command line just hangs. It sounds like you're trying to do that from Cygwin's mintty shell. The Windows Console infrastructure isn't particularly robust, so when a third-party program like mintty tries to run a

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

MS-DOS or DOS box is a misnomer. It is usually referred to as a "DOS Prompt" by those who think in clickety-pokery mode only. As far as I know, there is no "DOS" version of sqlite3. The Windows command line is a native Win32 Console Mode executable. It will run in any environment that

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

Also, I can't use the precompiled Windows binary to open databases created with whatever sqlite version the Cygwin Perl DBI uses, but I can use the cygwin sqlite3.exe to open databases created with the precompiled Windows binary. ___ sqlite-users mailing

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

My sqlite db seems to work when I access it from perl or java. It's only when I use the cygwin executable on the command line that it doesn't work. So all I really need to know is, How can I use the available Windows sqlite binary from http://www.sqlite.org/download.html on the cygwin command

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

Okay, but is there a simple answer for me, like getting a different build (eg the standard windows build)? I'm confused about the windows builds. There's a "sqlite-shell-win32 command-line shell", which looks like an executable, but it doesn't in fact work from the command line. I can only open

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

Warren, when you say "we may be switching the official builds back to Unix mode soon", you're referring only to the Cygwin builds, correct? The Win32 versions will still be generated as is? Personally, I've built a very specific VM to build from the Amalgamation source, however, I also keep the

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On 6/6/2013 21:56, Philip Goetz wrote: I think the problem is that the Cygwin distribution has the wrong version of SQLite, one built for unix. Nope. And even if true, it wouldn't be the right explanation. There are two major ways to build SQLite on Cygwin: 1. By default, building SQLite

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On 6/5/2013 11:25, Philip Goetz wrote: I suspect it's intercepting calls to the filesystem. Yes, the Cygwin DLL does translate POSIX paths to Windows paths internally. Then it calls the native APIs for you to give you the POSIX effect you asked for via the DLL. Part of the fun here is

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On 6/4/2013 09:22, Philip Goetz wrote: Is it caused by using a 32-bit sqlite3? > How does a 32-bit app access a 5G file? According to https://www.sqlite.org/limits.html, SQLite doesn't really have a 32-bit limit. It's not trying to load all 5 GiB into RAM at once. It manipulates the DB

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

I'm using Cygwin, a unix shell that runs under Windows. I don't know how cygwin interacts with the OS, but I have to specify cygwin-style paths rather than windows-style paths in perl to connect to the SQLite db, so I suspect it's intercepting calls to the filesystem. Using \ and * as characters

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

Good to know, however note that he's using /var/tmp which to me looks like linux, not windows. On Wed, Jun 5, 2013 at 5:41 AM, Clemens Ladisch wrote: > Stephen Chrzanowski wrote: > > I think the problem is with the \ (Note direction) as this makes the next > > character a

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

Stephen Chrzanowski wrote: > I think the problem is with the \ (Note direction) as this makes the next > character a literal character. Only for software that interprets backslashes in this way. The Windows file name parser doesn't. Regards, Clemens

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

I think the problem is with the \ (Note direction) as this makes the next character a literal character. So it isn't trying to drop the file into a sub directory, its using a literal character e. So /var/tmp/etilqs_PIREaghry4bPE*S8\et*ilqs_02LTi9u3HO3cx0g translates to

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On Tue, Jun 4, 2013 at 11:59 AM, Philip Goetz wrote: > On Tue, Jun 4, 2013 at 11:27 AM, Richard Hipp wrote: > > Try adding the command: > > > > .log stdout > > > > before running the CREATE INDEX and see what errors you get back. > > sqlite> .schema >

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On Tue, Jun 4, 2013 at 11:27 AM, Richard Hipp wrote: > Try adding the command: > > .log stdout > > before running the CREATE INDEX and see what errors you get back. sqlite> .schema CREATE TABLE taxon (gi INTEGER, taxon INTEGER); sqlite> .log stdout sqlite> create index

Re: [sqlite] An "unable to open database file" error that has nothing to do with opening database file

On Tue, Jun 4, 2013 at 11:22 AM, Philip Goetz wrote: > "unable to open database file" errors are usually caused by incorrect > file protection settings or directory protection settings, but I don't > think this one is. > > This is a 5.0G database with one table that I

[sqlite] An "unable to open database file" error that has nothing to do with opening database file

"unable to open database file" errors are usually caused by incorrect file protection settings or directory protection settings, but I don't think this one is. This is a 5.0G database with one table that I created in Windows 7 64-bit with sqlite3 3.7.16.2 from Perl. I can connect to the DB, read