Hi Monty
John> Um, that is not my point. The examples I gave to reproduce the problem
John> and the subject of this bug report is that "SELECT INTO OUTFILE" is
John> creating *world writeable* (not just readable) files. I only found
John> this problem trying to use mysqldump.
Sorry for misunderstanding this. I will see what I can do to fix so that
the file is only world readable in the next MySQL version.
Not a problem on the misunderstanding - that is usually the writer's
fault - not the reader's!
Rather than make the files world readable, could you please make the
files follow the UMASK environment variable that mysqld uses, or at
least use the umask of the user who is running the SELECT?
I read in the manual under file permissions:
`UMASK' The user-file creation mask when creating files.
and assumed that it would be used when writing to ALL files.
Regards
John