DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=n2O/mUQI1+xN8d6UcF4pXFxmsRr5khnMVMez+K/itvl
	+QKRsTPeDdokPSCs3W6/3m6DCuPNXqGCaZyO3f6lQygAacehhnYAJIL0wLTAyFRv
	zeExdi/xmrmd0DMfEEj/a9zG5DSRLYv8RkEL6LioFrzVX+rTTAFxzOcEOfSdB7G0
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51B6272F.8010001@etr-usa.com>
Date: Mon, 10 Jun 2013 13:21:19 -0600
From: Warren Young <warren@etr-usa.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: SQLite temporary path creation broken in latest stable release
References: <51B52B51.50203@dancol.org>
In-Reply-To: <51B52B51.50203@dancol.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 6/9/2013 19:26, Daniel Colascione wrote:
> which I haven't been able to test

You should.  One of the changes is to prefer creating temporary tables 
in memory instead of on disk, which should bypass the problem.

> "/var/tmp/etilqs_z28HceqmzVr3ZO1\\etilqs_rnPCuceSOgjfeTd".

This bug is already under discussion on the SQLite mailing list:

	http://comments.gmane.org/gmane.comp.db.sqlite.general/81718

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, since it knows such 
paths go through the Cygwin DLL, which sometimes has trouble doing the 
right thing with backslashes.

There is a chance the bug exists in the "Unix" path as well, since 
backslashes are legal in POSIX paths but not on Cygwin, but since the 
in-memory change will avoid this, my motivation to fix this bug twice is 
low.  Once should be enough.

--
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