On Mon, 23 Jun 2014 10:59:48 -0400, Scott Helms wrote:
> I generally drop them into /tmp for easy access and cleanup after the
> data load, but you can put them any place that the mysql daemon process
> has access to read.
Huh, maybe the daemon doesn't have access to /tmp?...
thufir@dur:/tmp$
Sol :-
Change file owner to mysql.mysql
OR
Change folder and file mode to 777
DK Sent from Phone
> On 23-Jun-2014, at 8:22 pm, thufir wrote:
>
> Apparently this error is because MySQL can't read my home directory? Fair
> enough, but I don't quite follow. Where would
Or use the LOCAL diective to have the client send the csv file contents
to the server.
/ Carsten
On 23-06-2014 16:59, Scott Helms wrote:
I generally drop them into /tmp for easy access and cleanup after the data
load, but you can put them any place that the mysql daemon process has
access to
Often, one uses /tmp or set up an appropriately premoissioned folder under /var
On Mon, Jun 23, 2014 at 10:52 AM, thufir wrote:
> Apparently this error is because MySQL can't read my home directory? Fair
> enough, but I don't quite follow. Where would be a good location for the
> CSV file, then
I generally drop them into /tmp for easy access and cleanup after the data
load, but you can put them any place that the mysql daemon process has
access to read.
Scott Helms
Vice President of Technology
ZCorum
(678) 507-5000
http://twitter.com/kscotthelms
Apparently this error is because MySQL can't read my home directory?
Fair enough, but I don't quite follow. Where would be a good location
for the CSV file, then?
thufir@dur:~$
thufir@dur:~$ mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
