Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Eugene Wu

The current database import process is like a toilet pipe. The pipe easily gets clogged if your data is a bit dirty. You gotta clean up the data, figure out the schema, figure out the types, etc etc. It really sucks! I once spent 2.5 hours importing two datasets from the FEC.

DBTruck is meant to turn the import process into a dump truck. Just throw data into it, should just work! Who cares about attribute names! Who cares about types you don't care about! You can clean it up later!

It assumes that your file is one tuple per line. Other than that, it will:

  • Automatically split up each line in a way that makes sense
  • Try to interpret each column's type
    • Currently supports int, float, date, time, timestamp
    • Defaults to varchar(100)
  • Make fake attribute names (attr0,…,attrN) so you don't need to
  • Import the file in blocks so that a single bad row doesn't blow the whole operation
    • It'll even pinpoint the specific bad rows and log them to an error file

DBTruck assumes that PostgreSQL is installed and running on your machine, and uses psql to load data.



I recommend installing dbtruck in a virtualenv environment. You can use pip to install dbtruck:

pip install dbtruck

This will install two scripts into your path -- and
The former is used to import data files into the database, and the latter can be used to quickly look at data in your database and rename/retype attributes.


For importmydata: -h data/testfile.txt tablename dbname

Running fixschema opens a prompt that supports commands. The following is an example of a session using fixschema:

  Schema Fixer is a simple interactive prompt for viewing your database
  and renaming attributes in your tables.

  Context: {}
  > connect test
  assuming test is database name and connecting to postgresql://localhost/test

  Context: {}
  > tables
                      a  2           actedin  2            actors  3
                      b  3  csp_perrow_aug10 11  csp_perrow_oct14 11
    csp_perrow_oct14_agg 12               fec 18            ground 31
                  india 31            movies  3               pcm 32
                sailors  1            states  2             times  3
                      us 31          zipcodes  9

  Context: {}
  > cols times
    227  character varying        wid    inferred str
      1  character varying  hittypeid    inferred str
    323   double precision          t  inferred float

  Context: {'table': 'times'}
  > col t
  Args used from Context: table = times

  times.t double precision        inferred type float

    48.0  171.0  128.0  167.0  257.0  468.0   98.0  186.0  184.0  179.0   53.0
    306.0   35.0   76.0  141.0  127.0   32.0    5.0  111.0  457.0  418.0  274.0
    320.0  313.0   84.0  325.0   11.0  226.0  116.0  298.0  173.0  159.0  341.0
    20.0   23.0   13.0  260.0   89.0   42.0  503.0   47.0  155.0  182.0  104.0
      2.0   82.0  102.0   88.0  163.0   95.0

  Context: {'table': 'times', 'col': 't'}
  >  CTL-D to exit


Immediate ToDos

  • Faster import: lots of datafiles have errors scattered throughout the data, which dramatically slows down bulk inserts.
    • Do preliminary filtering for errors
    • Fall back to (prepared) individual inserts once too many bulk insert attempts fail
  • Better error reporting
    • Load failed data into a hidden table in the database
    • Log error reasons
    • Try to recover from typical errors (date column contains a random string) by using reasonable defaults
  • Refactor file iterator objects to keep track of hints identified earlier in the pipeline
    • for example, parsed json files can infer that the dictionary keys are table headers -- no need to re-infer that later in the pipeline
    • Include confidence scores for each inference
  • Support extracting multiple tables from each input file
    • an HTML file may contain multiple tables to be imported
  • Support downloading URLS and HTML files
  • Support CSV output
  • Support Excel Files


If there are uses you would like to see, let me know! I'm adding features for what I want, but I'm interested in other uses.

In the future I would like to add

  • Good geocoder for location columns
    • support for simple location joins
  • support for other databases
  • let you specify port/host etc
  • support additional data file types (json, fixed offset, serialized)
  • support renaming and reconfiguring the tables after the fact
  • inferring foreign key relationships
  • creating indexes
  • interactive interface instead of requiring command line flags
  • and more!


just put my data in a database!







No releases published


No packages published