Guessing Table Structure from a Datafile

10.37.1 Problem

Someone gives you a datafile and says, "Here, put this into MySQL for me." But no table yet exists to hold the data.

10.37.2 Solution

Write the CREATE TABLE statement yourself. Or use a utility that guesses the table structure by examining the contents of the datafile.

10.37.3 Discussion

Sometimes you need to import data into MySQL for which no table has yet been set up. You can create the table yourself, based on any knowledge you might have about the contents of the file. Or you may be able to avoid some of the work by using, a utility located in the transfer directory of the recipes distribution. reads the datafile to see what kind of information it contains, then attempts to produce an appropriate CREATE TABLE statement that matches the contents of the file. This script is necessarily imperfect, because column contents sometimes are ambiguous. (For example, a column containing a small number of distinct strings might be a CHAR column or an ENUM.) Still, it's often easier to tweak the statement that produces than to write the entire statement from scratch. This utility also has a diagnostic function, though that's not its primary purpose. For example, you might believe a column contains only numbers, but if indicates that it should be created using a CHAR type, that tells you the column contains at least one non-numeric value. assumes that its input is in tab-delimited, linefeed-terminated format. It also assumes valid input, because any attempt to guess column types based on possibly flawed data is doomed to failure. This means, for example, that if a date column is to be recognized as such, it should be in ISO format. Otherwise, may characterize it as a CHAR column. If a datafile doesn't satisfy these assumptions, you may be able to reformat it first using the and utilities described in Recipe 10.19 and Recipe 10.32. understands the following options:


Interpret the first input line as a row of column labels and use them for table column names. If this option is omitted, uses default column names of c1, c2, and so forth. Note that if the file contains a row of labels and you neglect to specify this option, the labels will be treated as data values by The likely result is that the script will mischaracterize any numeric column as a CHAR column, due to the presence of a non-numeric value in the column.

--lower, --upper

Force column names in the CREATE TABLE statement to be lowercase or uppercase.


Quote table and column names in the CREATE TABLE statement with ` characters (for example, `mytbl`). This can be useful if a name is a reserved word. The resulting statement requires MySQL 3.23.6, because quoted names are not understood by earlier versions.


Generate a report rather than a CREATE TABLE statement. The script displays the information that it gathered about each column.

--tbl_name= tbl_name

Specify the table name to use in the CREATE TABLE statement. The default name is t.

Here's an example of how works, using the managers.csv file from the CSV version of the baseball database distribution. This file contains records for team managers. It begins with a row of column labels, followed by rows containing data values:


The first row indicates the column labels, and the following rows contain data records, one per line. requires input in tab-delimited, linefeed-terminated format, so to work with the managers.csv file, first convert it using, writing the result to a temporary file, managers.txt:

% --iformat=csv --ieol="
" managers.csv > managers.txt

Then run the temporary file through (the command shown here uses --lower because I prefer lowercase column names):

% --table=managers --labels --lower managers.txt > managers.sql

The CREATE TABLE statement that writes to managers.sql looks like this:

 lahmanid CHAR(9) NOT NULL,
 team CHAR(3) NOT NULL,
 div CHAR(1) NULL,
 plyrmgr CHAR(1) NULL,
); produces that statement based on deductions such as the following:

  • If a column contains only integer values, it's assumed to be an INT. If none of the values are negative, the column is likely to be UNSIGNED as well.
  • If a column contains no empty values, assumes that it's probably NOT NULL.
  • Columns that cannot be classified as numbers or dates are taken to be CHAR columns, with a length equal to the longest value present in the column.

You might want to edit the CREATE TABLE statement that produces, to make modifications such as increasing the size of character fields, changing CHAR to VARCHAR, or adding indexes. Another reason to edit the statement is that if a column has a name that is a reserved word in MySQL, you can change it to a different name. For example, the managers table definition created by contains a column named order, which is a reserved keyword. The column represents the order of the manager during the season (in case a team had more than one manager), so a reasonable alternative name is mgrorder. After editing the statement in the managers.sql file to make that change, execute it to create the table:

% mysql cookbook < managers.sql

Then you can load the datafile into the table (skipping the initial row of labels):

mysql> LOAD DATA LOCAL INFILE 'managers.txt' INTO TABLE managers

(When you do this, you'll notice that LOAD DATA reports some warnings. These are investigated further in Recipe 10.38.)

The database also is available in Access format. The Access database contains explicit information about the structure of the managers table, and this information is available to utilities like DBTools and MySQLFront that can use it to create the MySQL table for you. (See Recipe 10.39 for information about these programs.) This affords us the opportunity to see how well guesses the table structure using only the datafile, compared to programs that have more information available to them.

One problem with utilities like DBTools or MySQLFront is that if an Access table column has a name that is a reserved word, you cannot import it into MySQL without changing the Access table to use a different column name. This is the case for the Order column in the managers table. With, that wasn't a problem, because you can just edit the CREATE TABLE statement that it produces to change the name to something legal.[7] However, to deal with the Order column in the managers table for purposes of DBTools or MySQLFront, you should change the Access database itself to rename the column (for example, to MgrOrder.)

[7] Another approach is to use the --quote-names option when you run That allows you to create the table without changing the column name, although then you must put the name within backticks whether you refer to it.

The managers table structure produced by DBTools looks like this:

CREATE TABLE managers (
 LahmanID char(9) NOT NULL default '',
 Year int(11) default NULL,
 Team char(3) default NULL,
 Lg char(2) default NULL,
 Div char(2) default NULL,
 G int(11) default NULL,
 W int(11) default NULL,
 L int(11) default NULL,
 Pct double default NULL,
 Std int(11) default NULL,
 Half int(11) default NULL,
 MgrOrder int(11) default NULL,
 PlyrMgr char(1) default NULL,
 PostWins int(11) default NULL,
 PostLosses int(11) default NULL,
 KEY LahmanID (LahmanID)

MySQLFront creates the table like this:

CREATE TABLE managers (
 LahmanID longtext,
 Year int(11) default NULL,
 Team longtext,
 Lg longtext,
 Div longtext,
 G int(11) default NULL,
 W int(11) default NULL,
 L int(11) default NULL,
 Pct float default NULL,
 Std int(11) default NULL,
 Half int(11) default NULL,
 MgrOrder int(11) default NULL,
 PlyrMgr longtext,
 PostWins int(11) default NULL,
 PostLosses int(11) default NULL

Of the three programs, DBTools does the best job of determining the structure of the MySQL table. It uses the index information present in the Access file to write the KEY definition, and to create string columns with the proper lengths. MySQLFront doesn't produce the key definition and it defines strings as LONGTEXT columnseven the PlyrMgr column, which never contains a value longer than one character. The quality of the output produced by appears to be somewhere in between. It doesn't write the key definition, but neither does it write every string column as the longest possible type. (On the other hand, the column lengths are somewhat conservative.) All in all, that's not bad, considering that doesn't have available to it all the information contained in the original Access file. And you can use it on a cross-platform basis.

These results indicate that if you're using Windows and your records are stored in an Access file, you're probably best off letting DBTools create your MySQL tables for you. In other situations (such as when you're running under Unix or your datafile comes from a source other than Access), can be beneficial.

Using the mysql Client Program

Writing MySQL-Based Programs

Record Selection Techniques

Working with Strings

Working with Dates and Times

Sorting Query Results

Generating Summaries

Modifying Tables with ALTER TABLE

Obtaining and Using Metadata

Importing and Exporting Data

Generating and Using Sequences

Using Multiple Tables

Statistical Techniques

Handling Duplicates

Performing Transactions

Introduction to MySQL on the Web

Incorporating Query Resultsinto Web Pages

Processing Web Input with MySQL

Using MySQL-Based Web Session Management

Appendix A. Obtaining MySQL Software

Appendix B. JSP and Tomcat Primer

Appendix C. References

MySQL Cookbook
MySQL Cookbook
ISBN: 059652708X
EAN: 2147483647
Year: 2005
Pages: 412
Authors: Paul DuBois © 2008-2020.
If you may any questions please contact us: