Alvaro Herrera wrote:
Today, using --inputdir in pg_regress does not work for any other value
than something that resolves to cwd, since it will write a file to
"./sql", but try to read the same file from "<inputdir>/sql".
Maybe I'm missing something, but I don't see any reason why this is a
scenario worth supporting. What's the problem with cd'ing into the
directory containing the tests?
I agree - cd or some symlinks to cover up that the --inputdir parameter
does not work if you set it to anything except the default is a workaround.
Do we also agree that if you set --inputdir to anything other than the
default, pg_regress will not work (will write a file to one folder, and
try to read the same file from another)?
And if we agree above - should we make setting --inputdir work (read and
write from/to same directory), remove the --inputdir parameter (since
setting it to anything different from default value doesn't work), or
keep it there (to confuse people)?
-J
--
Jørgen Austvik, Software Engineering - QA
Sun Microsystems Database Group
begin:vcard
fn;quoted-printable:J=C3=B8rgen Austvik
n;quoted-printable:Austvik;J=C3=B8rgen
org:Sun Microsystems;Database Group
adr:;;Haakon VII gt. 7b;Trondheim;;NO-7485;Norway
email;internet:[EMAIL PROTECTED]
title:Senior Engineer
tel;work:+47 73 84 21 10
tel;fax:+47 73 84 21 01
tel;cell:+47 901 97 886
note:http://www.austvik.net/
x-mozilla-html:FALSE
url:http://blogs.sun.com/austvik/
version:2.1
end:vcard
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
