Hi Richard,
I'm not running MySQL on Windows, but I believe you may be looking at
file descriptors. Basically (at least in *nix), the shell keeps track
of open files through the use of file descriptors (numbers). The first
3 are already defined:
STDIN = 0
STDOUT = 1
STDIN = 2
By default, you can use input and output redirection with
metacharacters < and >. The 0 and 1 are assumed. However, it looks
like they are being prepended to the metacharacters (ie. 0< file for
input redirection and 1file for output redirection). If you want to
redirect errors (again, in *nix), you would have to use 2file.
Hope this helps,
Brian
Richard wrote:
Hi All,
I'm running MySQL version: 5.0.15-nt on WinXP-Pro/SP2.
Here's another batch anomoly:
I created a two-line batch file Invoke2CreateTableStmts.bat in a "db"
directory under the current directory.
mysql pmtallocmodel_test < db\CreatePmtsTbl.sql
mysql pmtallocmodel_production < db\CreatePmtsTbl.sql
I invoked it from a Command window with the command:
K:\db\Invoke2CreateTableStmts.bat
What I got was:
K:\mysql pmtallocmodel_test 0<db\CreatePmtsTbl.sql
K:\mysql pmtallocmodel_production 0<db\CreatePmtsTbl.sql
This time there was no parameter substution, but I got that gratuitous
"0" added. Despite the strange zero, the commands seem to have worked
correctly. Any idea where the zeros are coming from?
Thanks in Advance,
Richard