This is the mail archive of the
mailing list for the Cygwin project.
Re: SQLite temporary path creation broken in latest stable release
- From: Andrey Repin <anrdaemon at freemail dot ru>
- To: Warren Young <warren at etr-usa dot com>, cygwin at cygwin dot com
- Date: Thu, 13 Jun 2013 01:06:28 +0400
- Subject: Re: SQLite temporary path creation broken in latest stable release
- References: <51B52B51 dot 50203 at dancol dot org> <51B6272F dot 8010001 at etr-usa dot com> <1925072689 dot 20130612041943 at mtu-net dot ru> <51B8AB9F dot 4000602 at etr-usa dot com>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Warren Young!
>>> None of the SQLite core developers have responded to my charge that this
>>> looks like a bug in SQLite. It shouldn't be generating temporary file
>>> names with backslashes in them for Cygwin builds...
>> There's no reason to ever use backslashes in paths, ever.
> I suspect it is an interaction between #ifdef WINDOWS == true and the
> cygwinTempPath() hack patched into that version. The mainline SQLite
> code doesn't realize we've played a bit of sleight of hand with it, so
> it fails when it wants to add a second level to its temporary storage
> If true, that's yet another reason to switch to 3.7.17: I removed the
> hack since we're building as SQLITE_OS_UNIX.
I was referring to the fact, that Windows IO functions do not see a
difference between forward and backward slashes.
If you intend to write cross-platform application, you better off using
forward slashes internally in all cases.
Andrey Repin (firstname.lastname@example.org) 13.06.2013, <00:28>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple