Somewhere about Sat, 31-Jul-2004 at 11:17AM -0400 (give or take), Michael Stassen wrote:
|> With LOCAL, the *client* reads the file on the client's machine. |> Without LOCAL, the *server* reeads the file on the server's |> machine. Even though the client and server machines are the same |> in your case, those are still different operations. There are |> restrictions on having the server do the work, for good reason. |> This is documented in the manual |> <http://dev.mysql.com/doc/mysql/en/LOAD_DATA.html>: I'm pretty sure I understand the reasons. |> : For security reasons, when reading text files located on the server, |> : the files must either reside in the database directory or be readable |> : by all. Looks to me the mysql user should have no trouble with it: -rw-rw-r-- 1 pat pat 332 Jun 28 20:42 Orders.txt |> : Also, to use LOAD DATA INFILE on server files, you must have |> : the FILE privilege. See section 5.5.3 Privileges Provided by MySQL. Think we can count that one out as the problem since LOCAL which would have the same requirement does work. I can't be absolutely sure but I seem to remember I did not have this problem when I used 3.23.47 before I 'rpm -U'ed to 4.0.18. With the Redhat distro version, I could *not* use LOAD DATA LOCAL unless I started the client with --local-infile[=1] which seems to fit my understanding of the docs. With 4.0.18, it's unnecessary which was another surprise to me. Is there something I'm missing here? |> |> Michael Thanks Michael. -- ___ Patrick Connolly {~._.~} _( Y )_ Good judgment comes from experience (:_~*~_:) Experience comes from bad judgment (_)-(_) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
