Tom,
Thanks for that bit of insight on using the directories in Unix. I
originally tried no quotes or double quotes for my directory change and
no quotes worked for me. But after your mentioning the single quotes I
tested it out and those seem to work in Windows psql directory changes
as well.
Casey
Tom Lane wrote:
> Jorge Godoy <jgodoy@gmail.com> writes:
>> On Sunday 01 July 2007 22:25:24 Casey Crosbie wrote:
>>> Jorge,
>>> Thanks for the suggestion. But unfortunately, I tried both
>>> \cd "C:/Document~1" and just \cd C:/"Document~1" and neither worked.
>
>> Sorry. It should be up to 8 chars: "Docume~1" or some variation like that
>> (I've seen ~2 due to some unknown reason). This looks like a Windows
>> problem on finding directories with spaces in its name. The same happens
>> with diacriticals...
>
> FWIW, on a Unix machine I get
>
> $ mkdir "foo bar"
> $ psql regression
> Welcome to psql 8.2.4, the PostgreSQL interactive terminal.
>
> Type: \copyright for distribution terms
> \h for help with SQL commands
> \? for help with psql commands
> \g or terminate with semicolon to execute query
> \q to quit
>
> regression=# \cd foo bar
> \cd: could not change directory to "foo": No such file or directory
> regression=# \cd "foo bar"
> \cd: could not change directory to ""foo bar"": No such file or directory
> regression=# \cd 'foo bar'
> regression=# \!pwd
> /home/tgl/pgsql/foo bar
> regression=#
>
> So maybe single quotes would work better.
>
> I'm not sure if the behavior with double quotes should be considered a
> bug or not. Too lazy to check the manual, but I believe psql thinks
> single and double quotes are different.
>
> regards, tom lane
