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 in a filename is a spectacularly bad idea, even if Windows lets you do it this year. On Wed, Jun 5, 2013 at 12:57 PM, Stephen Chrzanowski <pontia...@gmail.com> wrote: > 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 <clem...@ladisch.de> wrote: > >> 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 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
