Bug #765 mysqlimport should read from stdin standard input
Submitted: 30 Jun 2003 10:34 Modified: 30 Nov 2005 19:47
Reporter: Steffen Möller Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Command-line Clients Severity:S4 (Feature request)
Version:Ver 3.4 Distrib 4.0.13 OS:Linux (Linux)
Assigned to: CPU Architecture:Any
Triage: Triaged: D5 (Feature request)

[30 Jun 2003 10:34] Steffen Möller
The usage of mysqlimport currently is
mysqlimport [OPTIONS] database textfile...

The textfile should be optional. It is currently needed to specify the table name the data should be imported into. Well, it needs an additional parameter then.

My motivation is that the EnsEMBL project (http://www.ensembl.org) is distributing very large datasets which parly even exceed the 2GB  These in a  gzipped format. I#d very much appreciate if I could pipe the output of gunzip -c to mysqlimport directly.

Best regards and many thanks for MySQL

Steffen Möller

How to repeat:

echo "<data>"|mysqlimport

Suggested fix:
Paramter --stdintablename=<tablename>
[8 Aug 2003 2:57] Lenz Grimmer
Assigned to Jani for consideration.
[5 Sep 2009 13:31] Edvárd Konrád Darabos
I believe it's a must because of security reasons. In multiuser environments you cannot place your input files simply into /tmp, you cannot make your home directory accessible to everyone. It makes me upset for years. :-(
[8 Sep 2009 8:48] Edvárd Konrád Darabos
Please ignore my last comment as I found the "--local" argument. Sorry!