Andrew Dunstan wrote:
>
>
> Claudio Natoli wrote:
>
> >>To the best of my knowledge, only the command processor cares about
> >>this, and you can get around it by quoting the command - see
> >>my initdb.c for examples. (this is also why I pass PGDATA via the
> >>
> >>
> >environment and
> >
> >
> >>never via the command line - the Windows command processor is
> >>quite dumb about multiple quoted strings). AFAIK direct library calls
> >>like stat() or fopen() should accept forward slashes. It may be that
> >>libraries other than MSVCRT act differently, although that would be very
> >>
> >>
> >odd,
> >
> >
> >>even for M$.
> >>
> >>
> >
> >They will, as long as there isn't a mix of forward and backward slashes,
> >which is currently the case in the backend code. Either canonicalize on
> >forward, or #define out backslashes in Win32. In either case, it is an
> >outstanding TODO item for postgres under win32.
> >
> >
> >
>
> Right. FWIW, I found canonicalization by far the simpler approach -
> which I adopted after tying myself in knots doing things the other way.
Added to Win32 project page:
Consistenly use forward slashes in paths, convert backslashes to
forward slashes
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073